Search squid archive

RE: Bypassing Squid for HTTP 1.1 chunked response f or WebApp Siebel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks Henrik for these information. I will check that.
Regards,
Mehdi

-----Original Message-----
From: Henrik Nordstrom [mailto:henrik@xxxxxxxxxxxxxxxxxxx] 
Sent: lundi 24 avril 2006 12:24
To: Mehdi Melhaa
Cc: Squid Users
Subject: Re:  Bypassing Squid for HTTP 1.1 chunked response for
WebApp Siebel


mån 2006-04-24 klockan 11:45 +0200 skrev Mehdi Melhaa:

> I encounter the same problem with my Siebel Web Application. I apply 
> the following instruction in squid.conf :
> 
> acl MySiebelCL dst 10.0.0.10/255.255.255.255
> header_access Accept-Encoding deny MySiebelCL
> 
> But I don't see any change. The response time are very slow. If I the 
> same access without the proxy/ the response time is better.
> 
> Do you have any idea ?

If your Siebel application is responding with chunked encoding in response
to requests from Squid you SHOULD discuss this with your Siebel support
contact as the server is in plain violation of the HTTP specifications.
Servers MUST NOT send chunked encoding to HTTP/1.0 clients (RFC 2616 3.6
Transfer Codings, last sentence). An application violating a MUST/MUST NOT
condition of the HTTP specifications is by definition non-compliant with the
specification.

But first, verify using squidclient or a similar siple client that the
application really is sending chunked encoding and that the problem is not
something else.

Regards
Henrik


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux