Dan Jacobson <[EMAIL PROTECTED]> writes:
> Normally in our browser when we hit Refresh in AddCacheInfo, the URL
> is something like
> http://jidanni1:8080/refresh/?http://pinyin.info/bla
> causing no cookies to be sent by the browser.
> Well, if the URL were instead
> http://pinyin.info/bla!WWWOFFLE-REFRESH-FLAG-TO-BE-STRIPPED
> then the cookies would be sent, and WWWOFFLE could strip the tag, no?
You are correct, the request that is recorded in the outgoing
directory is the when you follow this refresh URL, but then you get a
page that redirects you to the original cached page. This will mean
that cookies are not sent like you say. I am not really very happy
with needing the special URLs for POST and PUT requests that pretend
to be on the same host, but it is the only solution that I could think
of. For this special case it might also be that a special URL is
required that appears to be on the same host but which WWWOFFLE can
intercept.
You do have a refresh button on your browser that will do the right
thing and send the cookies, so all is not lost, you can refresh pages
with cookies.
--
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop [EMAIL PROTECTED]
http://www.gedanken.demon.co.uk/
WWWOFFLE users page:
http://www.gedanken.demon.co.uk/wwwoffle/version-2.9/user.html
