Please reply to the mailing list, not me direct, thanks.
On Fri, 2 May 2008, jess hampshire wrote:
2008/5/1 John-Mark Bell <[EMAIL PROTECTED]>:
Ok, this has now been reported on the bug tracker with a log file. The
answer is that NetSurf is being less tolerant of junk input than other
browsers. However, the URL you're redirecting to contains spaces. These
should be percent encoded (i.e replaced with %20).
At some point in the relatively near future, I'd expect NetSurf to handle
this case. It's not an entirely trivial fix, however.
When Netsurf can deal with invalid input, would it be a good idea for
it to prefix the referrer information reported to the site with
something like Invalid information from http://xxxx best guess
attempted? Or would that break standards?
Regardless of whether it broke standards (which it would, incidentally),
it'd break real-world web sites. Thus, it's not something we'd want to be
doing. Note also that the Referer header is not affected by HTTP
redirects (i.e. it is preserved across them).
John.
