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 (OK) or 304 (Not modified).
1) Issue with caching This could be related to the 304 responses, where no body is returned. 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 body. Does anyone know a way with Safari to see the actual HTTP response code returned? In Firefox there is the great LiveHttpHeaders extension. 2) Issue with HTTP server connector 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 connector. Best regards, Jerome > -----Message d'origine----- > De : Mike Moran [mailto:[EMAIL PROTECTED] > Envoyé : vendredi 27 octobre 2006 11:41 > À : [email protected] > 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 > >
