<feed xmlns='http://www.w3.org/2005/Atom'>
<title>nginx.git/src/http, branch release-1.5.11</title>
<subtitle>nginx</subtitle>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/'/>
<entry>
<title>SPDY: fixed potential integer overflow while parsing headers.</title>
<updated>2014-03-03T15:24:55+00:00</updated>
<author>
<name>Valentin Bartenev</name>
<email>vbart@nginx.com</email>
</author>
<published>2014-03-03T15:24:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=0c05e5b55fe799bb0d6330bcf75dbde370bf0ba6'/>
<id>0c05e5b55fe799bb0d6330bcf75dbde370bf0ba6</id>
<content type='text'>
Previously r-&gt;header_size was used to store length for a part of
value that represents an individual already parsed HTTP header,
while r-&gt;header_end pointed to the end of the whole value.

Instead of storing length of a following name or value as pointer
to a potential end address (r-&gt;header_name_end and r-&gt;header_end)
that might be overflowed, now r-&gt;lowercase_index counter is used
to store remaining length of a following unparsed field.

It also fixes incorrect $body_bytes_sent value if a request is
closed while parsing of the request header.  Since r-&gt;header_size
is intended for counting header size, thus abusing it for header
parsing purpose was certainly a bad idea.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Previously r-&gt;header_size was used to store length for a part of
value that represents an individual already parsed HTTP header,
while r-&gt;header_end pointed to the end of the whole value.

Instead of storing length of a following name or value as pointer
to a potential end address (r-&gt;header_name_end and r-&gt;header_end)
that might be overflowed, now r-&gt;lowercase_index counter is used
to store remaining length of a following unparsed field.

It also fixes incorrect $body_bytes_sent value if a request is
closed while parsing of the request header.  Since r-&gt;header_size
is intended for counting header size, thus abusing it for header
parsing purpose was certainly a bad idea.
</pre>
</div>
</content>
</entry>
<entry>
<title>SPDY: constant number of preallocated structures for headers.</title>
<updated>2014-03-03T15:24:54+00:00</updated>
<author>
<name>Valentin Bartenev</name>
<email>vbart@nginx.com</email>
</author>
<published>2014-03-03T15:24:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=3925c1b110ef13a3e4130e95a06cc85594bc4494'/>
<id>3925c1b110ef13a3e4130e95a06cc85594bc4494</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Request body: avoid potential overflow.</title>
<updated>2014-03-03T13:39:53+00:00</updated>
<author>
<name>Maxim Dounin</name>
<email>mdounin@mdounin.ru</email>
</author>
<published>2014-03-03T13:39:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=a2a26a7ce19ba8308cef5381456070fe599d0eb7'/>
<id>a2a26a7ce19ba8308cef5381456070fe599d0eb7</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Gzip static: fixed NGX_CONF_FLAG misuse.</title>
<updated>2014-03-03T13:17:25+00:00</updated>
<author>
<name>Valentin Bartenev</name>
<email>vbart@nginx.com</email>
</author>
<published>2014-03-03T13:17:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=2c0defac9b301293babf2520c0575d4a70aeee71'/>
<id>2c0defac9b301293babf2520c0575d4a70aeee71</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Disabled redirects to named locations if URI is not set.</title>
<updated>2014-02-27T16:36:35+00:00</updated>
<author>
<name>Maxim Dounin</name>
<email>mdounin@mdounin.ru</email>
</author>
<published>2014-02-27T16:36:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=96af3e9dfb1d890bbbbc78d88be8bb34a6e4d7a7'/>
<id>96af3e9dfb1d890bbbbc78d88be8bb34a6e4d7a7</id>
<content type='text'>
If something like "error_page 400 @name" is used in a configuration,
a request could be passed to a named location without URI set, and this
in turn might result in segmentation faults or other bad effects
as most of the code assumes URI is set.

With this change nginx will catch such configuration problems in
ngx_http_named_location() and will stop request processing if URI
is not set, returning 500.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
If something like "error_page 400 @name" is used in a configuration,
a request could be passed to a named location without URI set, and this
in turn might result in segmentation faults or other bad effects
as most of the code assumes URI is set.

With this change nginx will catch such configuration problems in
ngx_http_named_location() and will stop request processing if URI
is not set, returning 500.
</pre>
</div>
</content>
</entry>
<entry>
<title>Upstream: fixed error message wording.</title>
<updated>2014-02-20T09:48:40+00:00</updated>
<author>
<name>Konstantin Pavlov</name>
<email>thresh@nginx.com</email>
</author>
<published>2014-02-20T09:48:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=c539aaf352f5bf557d9f437105384c5589ec611a'/>
<id>c539aaf352f5bf557d9f437105384c5589ec611a</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Access: supplemented the obfuscated code with a comment.</title>
<updated>2014-02-19T17:45:27+00:00</updated>
<author>
<name>Ruslan Ermilov</name>
<email>ru@nginx.com</email>
</author>
<published>2014-02-19T17:45:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=3da53f339d37f03aaf5c60119898b235ee466a48'/>
<id>3da53f339d37f03aaf5c60119898b235ee466a48</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Upstream: ngx_post_event() instead of upgraded call (ticket #503).</title>
<updated>2014-02-18T13:30:40+00:00</updated>
<author>
<name>Maxim Dounin</name>
<email>mdounin@mdounin.ru</email>
</author>
<published>2014-02-18T13:30:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=5ec277847e8ff5a0990c03b93794d2e5d581f8e3'/>
<id>5ec277847e8ff5a0990c03b93794d2e5d581f8e3</id>
<content type='text'>
If a request is finalized in the first call to the
ngx_http_upstream_process_upgraded() function, e.g., because upstream
server closed the connection for some reason, in the second call
the u-&gt;peer.connection pointer will be null, resulting in segmentation
fault.

Fix is to avoid second direct call, and post event instead.  This ensures
that ngx_http_upstream_process_upgraded() won't be called again if
a request is finalized.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
If a request is finalized in the first call to the
ngx_http_upstream_process_upgraded() function, e.g., because upstream
server closed the connection for some reason, in the second call
the u-&gt;peer.connection pointer will be null, resulting in segmentation
fault.

Fix is to avoid second direct call, and post event instead.  This ensures
that ngx_http_upstream_process_upgraded() won't be called again if
a request is finalized.
</pre>
</div>
</content>
</entry>
<entry>
<title>Mp4: remove useless leading stsc entry in result mp4.</title>
<updated>2014-02-14T11:14:48+00:00</updated>
<author>
<name>Roman Arutyunyan</name>
<email>arut@nginx.com</email>
</author>
<published>2014-02-14T11:14:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=1dc1b0785b89743d637fa18e6d78a4999e2cf54c'/>
<id>1dc1b0785b89743d637fa18e6d78a4999e2cf54c</id>
<content type='text'>
The fix removes useless stsc entry in result mp4.
If start_sample == n then current stsc entry should be skipped
and the result stsc should start with the next entry.
The reason for that is start_sample starts from 0, not 1.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The fix removes useless stsc entry in result mp4.
If start_sample == n then current stsc entry should be skipped
and the result stsc should start with the next entry.
The reason for that is start_sample starts from 0, not 1.
</pre>
</div>
</content>
</entry>
<entry>
<title>SPDY: fixed reversed priority order in window waiting queue.</title>
<updated>2014-02-12T17:02:29+00:00</updated>
<author>
<name>Valentin Bartenev</name>
<email>vbart@nginx.com</email>
</author>
<published>2014-02-12T17:02:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sigsegv.uk/nginx.git/commit/?id=b20af091b7b656ad2d991ee1f8b81c72a1743cfa'/>
<id>b20af091b7b656ad2d991ee1f8b81c72a1743cfa</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
