On Thu, Feb 18, 2010 at 8:06 AM, Amos Jeffries squ...@treenet.co.nz wrote:
Thats what I described as weird. The server is not obeying that. It
challenged for every new object requested within link #7 in your trace.
Not sure what you mean by link 7, if you are refering to
GET
RFC 2616 states that 304 Not Modified responses don't have a body.
To quote from http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
If the client has performed a conditional GET request and access is
allowed, but the document has not been modified, the server SHOULD
respond with this
Jeff Foster wrote:
RFC 2616 states that 304 Not Modified responses don't have a body.
To quote from http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
If the client has performed a conditional GET request and access is
allowed, but the document has not been modified, the server SHOULD
I'm not sure which TCP stream you are referencing in your reply.
If you are looking at client port 1917; I agree with your response.
The problem as I see it is the TCP stream for the client port 1919.
It is using port 37159 on the squid server to the upstream. Then
in packet 210 the upstream
On Wed, 17 Feb 2010 08:59:27 -0600, Jeff Foster jfo...@gmail.com wrote:
I'm not sure which TCP stream you are referencing in your reply.
If you are looking at client port 1917; I agree with your response.
There are 7 distinct TCP streams/connections in that trace.
The first 6 display the
Henrik/Amos,
Did you get the tcpdumps? Is there anything else I can do to help
debug this problem?
Jeff F
2010/2/14 Jeff Foster
I am sending 2 tcpdump files as attachments to you, Henrik, and Amos plus the
mail list. I expect the mailing list will remove the attachments so I
hope you both
On Sat, Feb 13, 2010 at 4:13 AM, Amos Jeffries squ...@treenet.co.nz wrote:
Jeff Foster wrote:
On Thu, Feb 11, 2010 at 6:09 PM, Amos Jeffries squ...@treenet.co.nz
wrote:
Jeff Foster wrote:
There appears to be a problem with the connection pinning in both
versions squid-2.7.stable7 and
Can you please extend the trace to include the following two pieces of
information as well:
* The response. Both status code, and in case of 407 if there is an
NTLMSSP_CHALLLENGE blob or just the scheme name..
* Who closes the connection first (FIN)
lör 2010-02-13 klockan 14:17 -0600 skrev Jeff
There appears to be a problem with the connection pinning in both
versions squid-2.7.stable7 and
squid-3.1.0.7. I have some network captures that show the client
(IE6) creating multiple TCP
connections to the squid proxy and the proxy creating multiple TCP
connections to an IIS server.
Jeff Foster wrote:
There appears to be a problem with the connection pinning in both
versions squid-2.7.stable7 and
squid-3.1.0.7. I have some network captures that show the client
(IE6) creating multiple TCP
connections to the squid proxy and the proxy creating multiple TCP
connections to an
There appears to be a problem with the connection pinning in both
versions squid-2.7.stable7 and
squid-3.1.0.7. I have some network captures that show the client
(IE6) creating multiple TCP
connections to the squid proxy and the proxy creating multiple TCP
connections to an IIS server.
The
On Wed, 10 Feb 2010 12:53:16 -0600, Jeff Foster jfo...@gmail.com wrote:
There appears to be a problem with the connection pinning in both
versions squid-2.7.stable7 and
squid-3.1.0.7. I have some network captures that show the client
(IE6) creating multiple TCP
connections to the squid proxy
12 matches
Mail list logo
