Re: Caching servers in Local ISPs !!

Thanks for replying guyz. Can i use nginx (origin and edge) ? As the question in following link. http://stackoverflow.com/questions/10024981/distributed-cached-mp4-pseudostreaming-seeking-with-nginx If i use the origin and edge method, i think i'll change my application codes to redirect local

Re: subs filter error

That's the only upstream I'm aware of that works with proxies. On 09/05/2014 23:05, Jonathan Matthews wrote: On 9 May 2014 13:36, Tom McLoughlin m...@tommehm.com wrote: I keep getting this error every time someone loads a page. subs filter header ignored, this may be a compressed response.

Re: Caching servers in Local ISPs !!

See http://en.wikipedia.org/wiki/Content_delivery_network and http://en.wikipedia.org/wiki/File:Akamaiprocess.png Make yourself a HLD (high level design) before getting to technology. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,249997,250007#msg-250007

Strange advisory

I just saw something strange on http://nginx.org/en/security_advisories.html : An error log data are not sanitized Severity: none CVE-2009-4487 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-4487 Not vulnerable: none Vulnerable: all Severity is labelled as 'None', though the CVE talks,

Re: Strange advisory

Hello, This has not been fixed in current nginx releases, this is not directly related to nginx either, the problem is outdated terminal emulators would parse the potentially malicious commands in the log file. This answer http://unix.stackexchange.com/a/15210 explains it better. --- Regards,

RE: Strange advisory

Hi! I just saw something strange on http://nginx.org/en/security_advisories.html: An error log data are not sanitized Severity: none CVE-2009-4487 Not vulnerable: none Vulnerable: all Severity is labelled as 'None', though the CVE talks, among other stuff, about 'arbitrary

Re: nginx Digest, Vol 55, Issue 26

___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx -- next part -- An HTML attachment was scrubbed... URL: http://mailman.nginx.org/pipermail/nginx/attachments/20140510/b44f1a9a/attachment-0001.html

WSS Proxy to a Jetty AppServer

Hi, Im trying to proxy the wss (websockets) to a jetty server I have jetty server listening on 8085 http I've made the ssl proxy to the 8085 fine I've made the ws proxy to jetty ok getting web sockets connecting and transmiting data but wss is not working nginx 1.6.0 default:

Re: Strange advisory

I read the StackOverflow thread and it seems there are 2 teams ping-ponging the problem: - One says that it is a terminal problem and that control and escape sequences should not be executed - The other says that those features are userful and say that log files are supposed to be text-only, thus