Re: Safari/Mac Issues

[Henry Story]

Using tcpflow

[EMAIL PROTECTED]:0$ sudo tcpflow -i en1 -c host 82.103.129.162 > tcpflow.out

I get the following output:

tcpflow.out
Description: Binary data

Henry


On 27 Oct 2006, at 12:29, Jerome Louvel wrote:

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.

(OK) or 304 (Not modified).


1) Issue with caching

This could be related to the 304 responses, where no body is returned.

body.


returned? In Firefox there is the great LiveHttpHeaders extension.


2) Issue with HTTP server connector


connector.


Best regards,
Jerome

Thanks guys for the reports. Unfortunately I don't have access to Safari. Looking at my logs, Safari browsers get two types of HTTP response code: 200 Either Safari is passing a "If-Modified-Since" header but doesn't have the representation anymore in cache. Either Restlets are misinterpreting the header and return a 304 instead of a 200 with the representation in the Does anyone know a way with Safari to see the actual HTTP response code Currently, the web site uses the Simple HTTP connector. It may have some issues with Safari browsers... Did anyone tried to use different connectors locally with Safari. If so, it would be very helpful to know if the issue is occurring for all types of connectors (back to issue 1) or only the Simple

-----Message d'origine-----
De : Mike Moran [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 27 octobre 2006 11:41
À : discuss@restlet.tigris.org
Objet : Re: Safari/Mac Issues

Henry Story wrote:

This happened to me too. Also I don't always seem to get

the images.

Me too, on the images issue.

--
Mike Moran