stions/7996919/should-url-be-case-sensitive
On Wed, May 20, 2015 at 6:03 PM, itpp2012 wrote:
> J.J J Wrote:
> ---
> > No, exact and inclusive match are case sensitive.
> >
> > You can write it in two location :
> >
Check this out:
http://nginx.org/en/docs/http/ngx_http_rewrite_module.html#rewrite
On Sun, May 24, 2015 at 3:17 AM, escavern wrote:
> Hi guys, i really need some help here. I plan to move my forum from the
> root
> domain to a subfolder named "/forum"
>
> I need to rewrite from:
> www.mywebsite.
For http://www.mywebsite.com/image.php%3Fid%3D12345, the uri is
"/image.php?id=12345" after decoded,
so nginx may try to find file with name "image.php?id=12345" based on your
config file. That's why you got 404.
For http://www.mywebsite.com/image.php?id=12345, the uri is "/image.php"
and argument
No, exact and inclusive match are case sensitive.
You can write it in two location :
location = /test
location = /TEST
Personally, I think it's a bad practice to differentiate requests by the
case(ness) of URI.
On Tue, May 19, 2015 at 11:07 AM, E.B. wrote:
> I know how to do case insensi
If you access it correctly, nginx will send the request to backend and pass
response which is 302-redirect-link in your case back to the browser.
Check the "302-redirect-link", I think it should be an address to
http://192.168.15.159:7090 not to nginx(port 8064/8065), that's why the
browser bypass
Signal handler is ngx_signal_handler which in worker process does nothing
but log exit code and release possible holded mutexes, only master process
reap child by setting ngx_reap to 1 and spawn it in ngx_reap_children if
registed in ngx_processes(worker, loader, manager)
So no, you can't, but you
Hi, all:
nginx code version: 1.7.9 ( I have checked v1.9.0, no change about this)
The bufs used to invoke ngx_event_pipe_remove_shadow_links in
ngx_event_pipe_read_upstream come from p->preread_bufs or p->free_raw_bufs
or new allocated buf.
Both p->preread_bufs and new allocated buf have no sha
