RE: No hits!!! No SSL! Help, please!

> From: Nick Urbanik [SMTP:nicku@vtc.edu.hk]
>
> Please could you suggest a way of examining the headers?
>
        The client utility that comes with squid, or
        Lynx, although the former will have more
        predictable semantics.

> > Another is that the
> > browser has the page cached already and is doing an
> > If-Modified-Since request before squid has primed its
> > cache with the page.
>
> How do you suggest that I can detect this?
>
        941601387.887 3457 202.40.215.30 TCP_MISS/304 226 GET
http://www2.tyee.vtc.edu.hk/ - DIRECT/www2.tyee.vtc.edu.hk -

        Status 304 is "unchanged", meaning that the version in the browser
matches the
        version in the origin server. Because it is a TCP_MISS, rather than
a refresh,
        the cache doesn't have a copy, and because it is status 304, not
200, won't get
        a copy as a result of this request.

> > A third is that you are force
> > reloading the page to test the cache -
>
> Well, I am selecting "reload" from the browser menu (NS 4.7, Linux). Is
> that
> what you mean by "force reloading"?
>
        This was probably not quite right; a simple reload is normally
        OK, but shift (Netscape)/ control (IE) reload is a bad test.
        Generally, though, the client utility is probably safest.

> > on many browsers
> > this generates a no cache request as does accessing a
> > favourite.
> >
>
> Sorry to be so slow, but what should I do with SSL? I would like people
> on
> the outside world (outside the firewall) to be able to access our SSL
> server
>
        Tunnel it straight through, making sure that the certificate
        uses the same host name as that used to access the site (it
        is possible that some servers will object to certificates
        using their external name if that is not the name by which
        the server knows itself).

        The proxy has no visibility of the content of the request.

        Squid's normal SSL support requires that the browser know that
        a proxy is in use, although I haven't checked as to whether
        there are some special hacks for port 443 on transparent proxies.

        Note that a lot of your misses are status 503 (Service temporarily
        unavailable, e.g. overload) or status 404 (no such object).
Received on Wed Nov 03 1999 - 11:19:18 MST