thank you for the advice!
i tried doing that before though it did not work so i thought there could be
another solution..in any case tried that again, set it right before the
proxypass condition and it's still passing the type through...may i show u my
config to see what might be overrirding tha
Sorry, I forgot to post an example:
# curl -v -F file=@test.tar.gz -T http:/mydomain.com
* About to connect() to mydomain.com port 80 (#0)
* Trying 192.168.15.1... connected
* Connected to mydomain.com (192.168.15.1) port 80 (#0)
> POST / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-g
Hey!
I have this interesting issue.. I have a setup that looks like this Nginx <
- >Apache.. and when I try to upload files over proxy (nginx) then it gives
me: 413 Request Entity Too Large (by nginx).
Here is my config: http://pastebin.com/9t02sPtm
Also Apache and PHP both have 200mb upload lim
Version 2.3 is now available at:
http://labs.frickle.com/nginx_ngx_cache_purge/
GitHub repository is available at:
https://github.com/FRiCKLE/ngx_cache_purge/
Changes:
2014-12-23VERSION 2.3
* Fix compatibility with nginx-1.7.9+.
Best regards,
Piotr Sikora
___
Hello!
On Tue, Dec 23, 2014 at 05:10:09PM +0200, Roland RoLaNd wrote:
> one of my apps, specifically those on IOS forwarded a
> content-type header..this is causing my backend server to mess
> up its security signature check
> i need to be able to ignore content-type headers...
> assigning
Changes with nginx 1.7.9 23 Dec 2014
*) Feature: variables support in the "proxy_cache", "fastcgi_cache",
"scgi_cache", and "uwsgi_cache" directives.
*) Feature: variables support in the "expires" directive.
*) Feature: loading of secret
one of my apps, specifically those on IOS forwarded a content-type header..this
is causing my backend server to mess up its security signature check
i need to be able to ignore content-type headers...
assigning the header as empty "" does not work, (proxy_set_header
Accept-Encoding "";)and al
On Tue, Dec 23, 2014 at 05:58:00AM -0500, magal wrote:
Hi there,
> I have one domain and I want to serve different pages based on the Client
> IP.
>
> Nginx refuse different server with same server_name and both location must
> be / .
>
> Can you help me?
Set a variable based on the client IP
On Monday 22 December 2014 11:59:48 Jeroen Ooms wrote:
> I would like to use the gunzip module to serve cached, gzipped
> responses to clients that do not support gzip. I am running an Ubuntu
> 14.04 server. According to this post [1] the nginx-extras package
> includes support for gunzip, but when
I have one domain and I want to serve different pages based on the Client
IP.
Nginx refuse different server with same server_name and both location must
be / .
Can you help me?
Tnk
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,255744,255744#msg-255744
_
10 matches
Mail list logo