https://github.com/oroce/cached-node-http-proxy

Using node-http-proxy with cache middleware
https://github.com/oroce/cached-node-http-proxy

Last synced: about 1 month ago
JSON representation

Using node-http-proxy with cache middleware

• Host: GitHub
• URL: https://github.com/oroce/cached-node-http-proxy
• Owner: oroce
• Created: 2013-03-10T15:53:13.000Z (almost 12 years ago)
• Default Branch: master
• Last Pushed: 2013-03-17T14:41:38.000Z (almost 12 years ago)
• Last Synced: 2024-04-15T11:15:02.982Z (9 months ago)
• Language: JavaScript
• Size: 125 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
cached-node-http-proxy

======================

Using node-http-proxy with cache middleware

why

======================

I have an app (https://bitbucket.org/oroce/elvira-api/wiki/Home) which scrapes the hungarian train schedule website (http://mav-start.hu), under heavy load it's fuckin slow (sometimes the response could be more than 2-3 seconds), mostly between 6-9am and 5-8pm, so I've created this app to proxy requests and cache the response.

but why another app

======================

I know I could use varnish or squid, but I don't want, that's all.

I could even use connect-cache or sg like that, but caching for this service is based on query string/body parameters.