Ticket #492 (closed defect: fixed)

Opened 3 years ago

Last modified 14 months ago

False Content-Length on some 30x redirects

Reported by: conny Owned by: jan
Priority: normal Milestone:
Component: mod_proxy Version: 1.4.9
Severity: minor Keywords:
Cc: Blocked By:
Need User Feedback: Blocking:

Description

Consider the following request:

GET /foo HTTP/1.1
Host: baz

Say /foo is requested via mod_proxy which forwards the request to a backend where the /foo directory exists: 302 Moved Permanently -> "/foo/".

At least one popular web server out there insists on sending a short faux-HTML fragment with an <A>-link in addition to the "Location: ..." header. Therefore Content-Length might be > 0 on some requests. Lighttpd on the other hand takes a short route and simply skips sending the content part when it sees some status codes.

If we're gonna ignore any eventual content part, then we should make sure that the header is set correspondingly.

Attachments

lighttpd-redirect-content-length-zero.patch (0.5 kB) - added by conny 3 years ago.
If there was Content-Length, replace it

Change History

Changed 3 years ago by conny

If there was Content-Length, replace it

Changed 3 years ago by jan

  • status changed from new to closed
  • resolution set to fixed

fixed in changeset [985] by passing the content trough to the client as expected. The content-length is taken from the backend and passed through.

Add/Change #492 (False Content-Length on some 30x redirects)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.