Thanks Valentin for digging out the mod_security fix.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,255493,255528#msg-255528
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Tuesday 16 December 2014 00:58:26 akamatgi wrote:
> Hi Maxim/Valentin,
> Thanks for your response.
> Both port_start and port_end are being used by the mod_security nginx
> module.
> Failure to set port_start is causing a Segmentation Violation when
> mod_security is enabled and a request with a
Hi Maxim/Valentin,
Thanks for your response.
Both port_start and port_end are being used by the mod_security nginx
module.
Failure to set port_start is causing a Segmentation Violation when
mod_security is enabled and a request with absolute URI is sent.
Thanks,
-anirudh
Posted at Nginx Forum:
ht
Hello!
On Mon, Dec 15, 2014 at 07:45:06AM -0500, akamatgi wrote:
> Hi,
> I can see an issue in assigning the port_start and port_end members of
> ngx_http_request_t inside ngx_http_parse_request_line().
> If the request line has a absolute URI with explicit port specified, then
> port_end is set
On Monday 15 December 2014 07:45:06 akamatgi wrote:
> Hi,
> I can see an issue in assigning the port_start and port_end members of
> ngx_http_request_t inside ngx_http_parse_request_line().
> If the request line has a absolute URI with explicit port specified, then
> port_end is set correctly insid
Hi,
I can see an issue in assigning the port_start and port_end members of
ngx_http_request_t inside ngx_http_parse_request_line().
If the request line has a absolute URI with explicit port specified, then
port_end is set correctly inside ngx_http_parse_request_line():
...
case sw_port:
