[Zope3-dev] RE: Zope resources and browser caching

[Garrett Smith]

Philipp von Weitershausen wrote:
> Garrett Smith wrote:
>>> Hm, maybe that implementation is bad. tcpwatch will tell you for
>>> sure. 
>> 
>> So you're saying I should learn tcpwtch, eh? ;)
> 
> Not much to learn really:
> 
> Download tcpwatch.py and punch in (assuming that your Zope 3 instance
> is listening to 8080):
> 
> $ tcpwatch.py -s -L 9080:8080
> 
> Now point your browser to port 9080 instead of 8080 and see what
> happens on the console you started tcpwatch in. It prepends incoming
> and outgoing HTTP traffic with => and <= respectively. Feels like
> playing the CIA on your webserver...

This isn't working for me :-(

I can start tcpwatch and I get the output below when I hit it with my
browser, but nothing gets forwarded to the Zope server. The Zope server
accepts requests when hit directly.

 -- Garrett




Forwarding :9090 -> :8080
[00:00.000 - client 127.0.0.1:2769 forwarded to :8080]
==>GET / HTTP/1.1
==>Host: localhost:9090
==>User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6)
Gecko/20050223 Firefox/1.0.1
==>Accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plai
n;q=0.8,image/png,*/*;q=0.5
==>Accept-Language: en-us,en;q=0.5
==>Accept-Encoding: gzip,deflate
==>Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
==>Keep-Alive: 300
==>Connection: keep-alive
==>Cookie:
zope3_cs_681fbd4=VM8xwzDQsigqSikv.LNwNY9gYtsgfqCWEqPpuF7yabn5uZCg4k6Mco
==>