Dan Jacobson <[EMAIL PROTECTED]> writes:
> Gentlemen, I hereby expose a bug or a special case etc. that eats POST
> contents if you ever do wwwoffle -o, -O on them. Note where 620 becomes 136:
> $ wwwoffle-ls outgoing
> OwBEjpuEtlQ8mygZ4Z1NTow 620 Feb 3 4:55 http://bla.bla/bla.fpl?!POST:bla
> $ wwwoffle-ls outgoing|awk '{print $NF}'|xargs wwwoffle
> Getting: http://bla.bla/bla.fpl?!POST:bla
> $ wwwoffle-ls outgoing
> OwBEjpuEtlQ8mygZ4Z1NTow 620 Feb 3 4:55 http://bla.bla/bla.fpl?!POST:bla
> $ wwwoffle-ls outgoing|awk '{print $NF}'|xargs wwwoffle -o
> The URL is not in the cache but has been requested.
> $ wwwoffle-ls outgoing
> OwBEjpuEtlQ8mygZ4Z1NTow 136 Feb 3 4:58 http://bla.bla/bla.fpl?!POST:bla
>
> Indeed, doing wwwoffle -o, -O on URLs that are in outgoing, but not in
> the cache, will cause all their headers to go bye bye and become just
> Pragma: wwwoffle-client etc. One might argue what business does one
> have doing wwwoffle -o on items that are in outgoing but not in the
> cache... argue one might...
It is even worse than that, if you use your browser to request the URL
then the same thing happens.
I have now put a test in so that if an outgoing file exists for a URL
then a new request for the same URL will not be overwritten.
--
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop [EMAIL PROTECTED]
http://www.gedanken.demon.co.uk/
WWWOFFLE users page:
http://www.gedanken.demon.co.uk/wwwoffle/version-2.8/user.html
