Project

General

Profile

Actions
Copy link

Bug #492

closed

False Content-Length on some 30x redirects

Added by conny about 19 years ago. Updated almost 18 years ago.

Status:
Fixed
Priority:
Normal
Category:
mod_proxy
Target version:
-
ASK QUESTIONS IN Forums:

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.

Files

lighttpd-redirect-content-length-zero.patch (525 Bytes) lighttpd-redirect-content-length-zero.patch If there was Content-Length, replace it conny, 2006-02-03 00:35
Actions
Copy link
 #1

Updated by jan about 19 years ago

  • Status changed from New to Fixed
  • Resolution set to fixed

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

Actions
Copy link

Also available in: Atom