Thanks! Setting "underscores_in_headers on;" fixed the issue and X_FORWARDED_PROTO is being carried forward now.by jaychris - Nginx Mailing List - English
Running Nginx 1.2.7 behind HAproxy, with SSL being terminated on on HAproxy. I was using the X_FORWARDED_PROTO header to make some decisions on the backend when I was using Apache, but it doesn't look like Nginx is handling the header currently: client sent invalid header line: "X_FORWARDED_PROTO: http" while reading client request headers, I found an old thread that seemed to addby jaychris - Nginx Mailing List - English
Well, true, but .mov is still h.264 encoded, so I believe it would still use the same streaming mechanism. Maybe I'm wrong about that. At any rate, it appears to be working now that I fixed my nginx location filters. Lukas Tribus Wrote: ------------------------------------------------------- > ..mov is not .mp4, they are completely different containers. > > > > -------by jaychris - Nginx Mailing List - English
Once again, never mind. I had a bad location filter.by jaychris - Nginx Mailing List - English
I'm running Nginx v1.2.7 from the Nginx repo, with mp4 module enabled. I added this to my conf: location ~ \.mov { mp4; mp4_buffer_size 1m; mp4_max_buffer_size 5m; } location / { try_files $uri $uri/ @rewrite; } location @rewrite { # Some modules enforce no slasby jaychris - Nginx Mailing List - English
Never mind, I guess there are two configure statements in the spec file. I added the module to both and it's working fine.by jaychris - Nginx Mailing List - English
I'm trying to compile in the nginx_upload_progress module into an RPM. I'm using the SPEC file provided with v1.2.7 from the Nginx repos. I downloaded the upload_progress module, opened up the source tar archive, copied the module to nginx-1.2.7/nginx-upload-progress-module, and added this line to my SPEC file: --add-module=%{_builddir}/%{name}-%{version}/nginx-upload-progress-module \ Wheby jaychris - Nginx Mailing List - English