I've also noticed that the Simple HTTP connector adds an extra "Transfer-Encoding: chunked" header to all responses, including those that don't have a response. That may cause some troubles to Safari.
Jerome > -----Message d'origine----- > De : Jerome Louvel > Envoyé : mercredi 1 novembre 2006 11:20 > À : [email protected] > Objet : RE: Safari/Mac Issues > > > Hi Henry, > > Thanks for the traces, it is a problem related to the caching > of response entities. When you reloaded the page, the server > replied with 304 status codes (Not Modified) which seems accurate. > > For some reason, Safari isn't able to interpret these > response in order to use its internal cache and display the pictures. > > Henry, it would be useful if you could seems me the traces > following these steps: > - Empty the browser cache > - Restart Safari > - Enable tcpflow > - Go to http://www.restlet.org > - Press "Reload" > - Press "Shift" + "Reload" > - Press "Reload" > - Disable tcpflow > > Merci :-) > Jerome > > > -----Message d'origine----- > > De : Henry Story [mailto:[EMAIL PROTECTED] > > Envoyé : vendredi 27 octobre 2006 14:10 > > À : [email protected] > > Objet : Re: Safari/Mac Issues > > > > Using tcpflow > > > > [EMAIL PROTECTED]:0$ sudo tcpflow -i en1 -c host 82.103.129.162 > > tcpflow.out > > > > I get the following output: > > > > > > I would not be surprised if it is a Safari issue, as I have noticed > > something similar on the rollerwebloger.org site last week. > > > > The first download showed the pictures, the second one did not. The > > reload that lead to the above tcpflow.out file did not lead > to the picture being re-loaded. > > > > Henry >
