Julien Gerhards wrote:
Hi,

I'm on CentOS 5.2 with the last Apache 2.2.3
It's configured like a proxy cache for a lan (caching internet)

What i expect?
A fully transparent proxy!

the request URL : www.clubic.com

Thru Apache the title is : Clubic : Informatique et Multim�dia
Without the proxy : Clubic : Informatique et Multimédia


Much, much better.
Now we have something to start with.

I accessed the original site, using Firefox 3.1 with the HttpFox extension. That allows me to see what my browser sends as a HTTP request, and to see what the server answers, including the HTTP headers. (If you are using IE as a browser, a comparable extension is called Fiddler2).

The request was :
(Request-Line)  GET / HTTP/1.1
Host    www.clubic.com
User-Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3
Accept  text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language en-gb,en;q=0.7,de-de;q=0.3
Accept-Encoding gzip,deflate
Accept-Charset  ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive      300
Connection      keep-alive

The response was :
(Status-Line)   HTTP/1.1 200 OK
Date    Tue, 19 May 2009 16:19:08 GMT
Server  Apache-AdvancedExtranetServer
X-Powered-By    PHP/4.3.10
Set-Cookie id_search=680299286; expires=Tue, 19-May-2009 17:19:08 GMT; path=/; domain=.clubic.com
Etag    "cyrealis--30836763.114748"
Content-Encoding        gzip
Vary    Accept-Encoding,User-Agent
Cache-Control   max-age=0
Expires Tue, 19 May 2009 16:19:08 GMT
Connection      close
Transfer-Encoding       chunked
Content-Type    text/html

In other words, the original server is not sending a "charset" along with the Content-type response header. That is not very good, but the default should be iso-8859-1.

In the html page itself, there is a line saying :
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
(That, I see when viewing the "source" text of the page, in the browser).

Now, to compare with what your proxying Apache is doing, you should use a browser with one the extensions above, call the same URL, and compare the response you get from your Apache proxy, to the response above (without proxy).


Note on my earlier response :

It may well be that there is some kind of problem in Apache's proxy module, or cache module, or a misconfiguration. But the point is, without knowing what you are really doing, it is impossible to give you any useful information.

Also, when you just say that you "use Apache as a proxy", it is not very indicative. Apache can be used as a forward proxy (like you are doing), or as a reverse proxy, for example to a back-end Tomcat server. And only as such a reverse proxy to Tomcat, there are 3 different ways (and 3 different modules at the Apache level) in which this can be done.


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [email protected]
  "   from the digest: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to