Re: mod_proxy drops the content-length header
On Fri, Jul 26, 2002 at 11:46:45AM -0400, [EMAIL PROTECTED] wrote: In case anyone is interested, here are some captures taken with Sniffer Pro. The key things to note are that Apache 2.0.39 mod_proxy drops the Content-Length header, and also that it inserts Content-Type: text/plain. This behaviour is causing Web-Polygraph to report superfluous errors. Section 13.5.2 of 2616 seems to have some thoughts on this, but the wording seems a bit muddled. A Content-Length is a end-to-end header (generally non-modifiable), and 13.5.2 says: The Content-Length field of a request or response is added or deleted according to the rules in section 4.4. A transparent proxy MUST preserve the entity-length (section 7.2.2) of the entity-body, although it MAY change the transfer-length (section 4.4). I believe it would be possible for the proxy to delete the content-length header and replace it with another mechanism of its choosing to signal the entity-length. But, the question is whether we want to also send the C-L (if known) when doing a connection close. That's an option. As far as adding Content-Type, section 13.5.2 says: A proxy MUST NOT modify or add any of the following fields in a message that contains the no-transform cache-control directive, or in any request: ... - Content-Type ... I'm not sure how to parse the 'or in any request' bit. Does that apply to all requests or just those with no-transform cache-control set? If it is free to modify it, then I think I can make a case that the DefaultType directive applies. But, I'm not 100% sold on that, either. -- justin
Re: mod_proxy drops the content-length header
On Sat, 27 Jul 2002, Justin Erenkrantz wrote: On Fri, Jul 26, 2002 at 11:46:45AM -0400, [EMAIL PROTECTED] wrote: In case anyone is interested, here are some captures taken with Sniffer Pro. The key things to note are that Apache 2.0.39 mod_proxy drops the Content-Length header, and also that it inserts Content-Type: text/plain. This behaviour is causing Web-Polygraph to report superfluous errors. Section 13.5.2 of 2616 seems to have some thoughts on this, but the wording seems a bit muddled. See also: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8677 Joshua.
RE: cvs commit: httpd-2.0/docs/manual env.xml filter.xml handler.xml env.html.en filter.html.en handler.html.en
Silly question, but why aren't we using DocBook for this? -- James
RE: cvs commit: httpd-2.0/docs/manual env.xml filter.xml handler.xmlenv.html.en filter.html.en handler.html.en
On Sat, 27 Jul 2002, James Cox wrote: Silly question, but why aren't we using DocBook for this? Not really a silly question. It was debated extensively, although not necessarily on this list. (I tried to start the debate here, but most not many people seemed insterested in arguing the other side.) Some of my opinions on the topic are http://www.apachelabs.org/httpd-docs/200107.mbox/%3CPine.WNT.4.33.0107262016130.-2033491-10@jgcomputer%3E and http://www.apachelabs.org/httpd-docs/200202.mbox/%3CPine.WNT.4.33.0202122137250.-1759159-10@jgcomputer%3E To summarize a few on the key reasons: - Docbook doesn't have the semantic structure to properly mark-up an HTTP Server manual. It is designed for a programming language, and we would need to really warp some of the meaning to get it to work for us. This is particularly true in the module documentation, but is also somewhat true in the rest of the docs. - The current format is heavily based on xhtml, and therefore it is rather easy to convert the current docs to this format. - Docbook is somewhat difficult to use. It has tons of tags (although this could be partly solved by using one of the simple docbook dtds) and some things like the table markup are very obtuse. My other response to this question is that, regardless of the format that we choose, more structure is better. So, for example, I would guess that if we later decide to go with docbook, it should be possible to write some xslt to transform the current format into something close to docbook. Doing the same from raw xhtml would be much more difficult. When I've been adding new tags (as opposed to borrowing from xhtml), I've tried to match them as closely as possible to docbook. But I can't claim I've been entirely successful in that. Joshua.
Vacation reminder
Just a reminder than I'm taking vacation until Aug 4th, and therefore have very limited 'Net access :) -- === Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ A society that will trade a little liberty for a little order will lose both and deserve neither - T.Jefferson
Quick question.
Anyone ever seen a browser report Error -12263 when connecting to apache via SSL? I've never seen this error, and we've never gotten it before, so I was curious. TIA. -- Austin Gonyou [EMAIL PROTECTED] Coremetrics, Inc.
