https://redmine.lighttpd.net/https://redmine.lighttpd.net/favicon.ico?13667327412019-02-09T16:09:54Zlighty labsLighttpd - Feature #2933: GET/HEAD with content-lengthhttps://redmine.lighttpd.net/issues/2933?journal_id=116632019-02-09T16:09:54Zgstrauss
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Invalid</i></li></ul><blockquote><blockquote>
<p>(request.c.1163) GET/HEAD with content-length -> 400</p>
</blockquote></blockquote>
<blockquote>
<p>I've got quite a few of these in my logs. Does it make sense to log these?</p>
</blockquote>
<p><a class="external" href="https://tools.ietf.org/html/rfc7231#section-4.3.1">https://tools.ietf.org/html/rfc7231#section-4.3.1</a><br />4.3.1. GET<br />...<br /> A payload within a GET request message has no defined semantics;<br /> sending a payload body on a GET request might cause some existing<br /> implementations to reject the request.</p>
<p><a class="external" href="https://tools.ietf.org/html/rfc7231#section-4.3.2">https://tools.ietf.org/html/rfc7231#section-4.3.2</a><br />4.3.2. HEAD<br />...<br /> A payload within a HEAD request message has no defined semantics;<br /> sending a payload body on a HEAD request might cause some existing<br /> implementations to reject the request.</p>
<p>.</p>
<blockquote>
<p>If yes, some more info like IP and UA would be handy.</p>
</blockquote>
<p>There is already an option to log Content-Length in mod_accesslog, as there are for IP and User-Agent.</p>
<blockquote>
<p>If not, could you stop logging them?</p>
</blockquote>
<p>Similar to numerous other places logging errors during request processing, I may consider logging this only if <code>debug.log-request-header-on-error = "enable"</code> . This may or may not occur as a side effect of my refactoring of the request processing code.</p> Lighttpd - Feature #2933: GET/HEAD with content-lengthhttps://redmine.lighttpd.net/issues/2933?journal_id=116652019-02-10T09:53:06ZOlaf-van-der-Spek
<ul></ul><p>gstrauss wrote:</p>
<blockquote><blockquote><blockquote>
<p>(request.c.1163) GET/HEAD with content-length -> 400</p>
</blockquote></blockquote>
<blockquote>
<p>I've got quite a few of these in my logs. Does it make sense to log these?</p>
</blockquote></blockquote>
<blockquote>
<p>...</p>
</blockquote>
<p>Is that a yes or a no? ;)</p>
<blockquote><blockquote>
<p>If yes, some more info like IP and UA would be handy.</p>
</blockquote>
<p>There is already an option to log Content-Length in mod_accesslog, as there are for IP and User-Agent.</p>
</blockquote>
<p>This is about error.log, not access.log.</p>
<blockquote><blockquote>
<p>If not, could you stop logging them?</p>
</blockquote>
<p>Similar to numerous other places logging errors during request processing, I may consider logging this only if <code>debug.log-request-header-on-error = "enable"</code> . This may or may not occur as a side effect of my refactoring of the request processing code.</p>
</blockquote>
<p>Great</p>