Reloading pages
Stephen Fitzpatrick
sfitzp at cs.qub.ac.uk
Sat Mar 4 08:17:48 PST 1995
Joe Pasqua <pasqua at mv.us.adobe.com>:
> Go to any page, say http://akebono.stanford.edu/yahoo/. It loads
> fine. Reload the page. A "Request Failed"dialog comes up saying:
> Access forbidden by rule http://<proxy server
> here>/http://akebono.stanford.edu/yahoo/
I believe the reload problems are caused by OW adding an extra / to the URL
before prepending the proxy/caching server's URL. For example, my proxy's log
shows requests such as
GET http://akebono.stanford.edu/yahoo/ HTTP/1.0
for the first request for a page, but
GET /http://akebono.stanford.edu/yahoo/ HTTP/1.0
when I reload the page. This was indeed reported a while back, but is still
present in PR1.2 (under NextStep 3.0).
There is a workaround if you have access to your proxy server's configuration:
add a line to translate incorrect requests. For example, for the CERN (3.0)
daemon
Map /http:* http:*
(this should appear *before* the PASS line for http proxying).
A similar line should probably be added for each protocol that is proxied.
John Soward <soward at dab.slip.uky.edu>:
> Also note that if your proxy server has caching enabled, you will
> never be able to reload correctly...this is not a problem with
> OmniWeb...I've been able to re-load okay most of the time while
> using a CERN proxy server with caching turned off...
That's interesting: I've no problem using the caching proxy with any other
browser (lynx, XMosaic - horrible experience that), so I assume it is an OW
problem. It may be that the proxy/no-cache configuration manages to correct
the incorrect URLs OW seems to be sending to the proxy.
--
Stephen Fitzpatrick | Email: S.Fitzpatrick at cs.qub.ac.uk
Dept. of Computer Science | ASCII, NeXT (maybe MIME): PGP via WWW
Queen's Univ. of Belfast |<URL:http://www.cs.qub.ac.uk/~S.Fitzpatrick/>
More information about the OmniWeb-l
mailing list