You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Martin Kraemer <Ma...@Fujitsu-Siemens.com> on 2002/03/14 12:25:47 UTC
Apache-1.3 proxy: X-Cache question
--snip--
% netcat localhost 8080 << .
HEAD http://apache.org/favicon.ico HTTP/1.0
.
HTTP/1.1 200 OK
Date: Thu, 14 Mar 2002 11:20:48 GMT
Server: Apache/1.3.24-dev (Unix)
Accept-Ranges: bytes
Cache-Control: max-age=86400
Content-Length: 766
Content-Type: text/plain
ETag: "1f8f-2fe-adc4b1c0"
Expires: Fri, 15 Mar 2002 11:20:49 GMT
Last-Modified: Mon, 24 Sep 2001 02:07:11 GMT
Via: 1.1 localhost:8080 (Apache/1.3.24-dev)
X-Cache: MISS from localhost
Connection: close
--snip--
Should the X-Cache line not rather read:
X-Cache: MISS from localhost:8080
because that was its port number?
RFC2616 doesn't describe X-Cache ;-)
Martin
--
<Ma...@Fujitsu-Siemens.com> | Fujitsu Siemens
Fon: +49-89-636-46021, FAX: +49-89-636-47655 | 81730 Munich, Germany
Re: Apache-1.3 proxy: X-Cache question
Posted by Graham Leggett <mi...@sharp.fm>.
Martin Kraemer wrote:
> X-Cache: MISS from localhost
> --snip--
>
> Should the X-Cache line not rather read:
>
> X-Cache: MISS from localhost:8080
>
> because that was its port number?
I suppose it should, yes.
Regards,
Graham
--
-----------------------------------------
minfrin@sharp.fm "There's a moon
over Bourbon Street
tonight..."
Re: Apache-1.3 proxy: X-Cache question
Posted by Sander van Zoest <sa...@vanzoest.com>.
On Thu, 14 Mar 2002, Martin Kraemer wrote:
> On Thu, Mar 14, 2002 at 12:25:47PM +0100, Kraemer, Martin wrote:
> > X-Cache: MISS from localhost
> > Should the X-Cache line not rather read:
> > X-Cache: MISS from localhost:8080
> I just looked at squid's implementation. It doesn't append the port
> either. But IMHO that's a bug too.
In the case of Squid it could be that the request was made via HTCP or
ICP rather then HTTP. So the port number might still be useful, but
it might be that HTTP is not spoken on this port number.
--
Sander van Zoest sander@vanzoest.com
San Diego, CA, US http://Sander.vanZoest.com/
Re: Apache-1.3 proxy: X-Cache question
Posted by Martin Kraemer <Ma...@Fujitsu-Siemens.com>.
On Thu, Mar 14, 2002 at 12:25:47PM +0100, Kraemer, Martin wrote:
> X-Cache: MISS from localhost
>
> Should the X-Cache line not rather read:
>
> X-Cache: MISS from localhost:8080
I just looked at squid's implementation. It doesn't append the port
either. But IMHO that's a bug too.
Martin
--
<Ma...@Fujitsu-Siemens.com> | Fujitsu Siemens
Fon: +49-89-636-46021, FAX: +49-89-636-47655 | 81730 Munich, Germany
Re: Apache-1.3 proxy: X-Cache question
Posted by Jim Jagielski <ji...@jaguNET.com>.
The latest CVS appears correct... could someone else confirm?
At 5:52 PM +0100 3/15/02, dirkx@covalent.net wrote:
>On Thu, 14 Mar 2002, Martin Kraemer wrote:
>
>> --snip--
>> % netcat localhost 8080 << .
>> HEAD http://apache.org/favicon.ico HTTP/1.0
>>
>> .
>> HTTP/1.1 200 OK
>> Date: Thu, 14 Mar 2002 11:20:48 GMT
>> Server: Apache/1.3.24-dev (Unix)
>...
>> X-Cache: MISS from localhost
>> Connection: close
>> --snip--
>>
>> Should the X-Cache line not rather read:
>>
>> X-Cache: MISS from localhost:8080
>>
>> because that was its port number?
>
>Yes - and anoyingly squid and various other cache flow mngt products get
>this wrong as well.
>
>> RFC2616 doesn't describe X-Cache ;-)
>
>There are some internet draft trying to get this properly documented.
>
>Dw
--
===========================================================================
Jim Jagielski [|] jim@jaguNET.com [|] http://www.jaguNET.com/
"A society that will trade a little liberty for a little order
will lose both and deserve neither" - T.Jefferson
Re: Apache-1.3 proxy: X-Cache question
Posted by di...@covalent.net.
On Thu, 14 Mar 2002, Martin Kraemer wrote:
> --snip--
> % netcat localhost 8080 << .
> HEAD http://apache.org/favicon.ico HTTP/1.0
>
> .
> HTTP/1.1 200 OK
> Date: Thu, 14 Mar 2002 11:20:48 GMT
> Server: Apache/1.3.24-dev (Unix)
...
> X-Cache: MISS from localhost
> Connection: close
> --snip--
>
> Should the X-Cache line not rather read:
>
> X-Cache: MISS from localhost:8080
>
> because that was its port number?
Yes - and anoyingly squid and various other cache flow mngt products get
this wrong as well.
> RFC2616 doesn't describe X-Cache ;-)
There are some internet draft trying to get this properly documented.
Dw