In article <[email protected]>, Richard Porter <[email protected]> wrote: > The "Bad redirect URL" problem has been around for a long time. I have > probably raised a bug report for it but I can't remember when.
If it's any help, I get the following when I try fetching a blocked site via wget *wget -S --spider http://www.domai.com --11:46:42-- http://www.domai.com/ => `index.html' Resolving www.domai.com... 64.38.197.113 Connecting to www.domai.com[64.38.197.113]:80... connected. HTTP request sent, awaiting response... 1 HTTP/1.1 307 Temporary Redirect 2 Location: http://192.168.1.1/webfilter/blockpage?nonce=e2c01ae50a9a2c79&tid=10 3 Content-Type: text/plain 4 Content-Length: 0 5 Connection: Keep-Alive Location: http://192.168.1.1/webfilter/blockpage?nonce=e2c01ae50a9a2c79&tid=10 [following] --11:46:43-- http://192.168.1.1/webfilter/blockpage?nonce=e2c01ae50a9a2c79&tid=10 => `blockpage?nonce=e2c01ae50a9a2c79&tid=10' Connecting to 192.168.1.1:80... connected. HTTP request sent, awaiting response... 1 HTTP/1.1 200 OK 2 Date: Tue, 20 Jan 2009 11:46:44 GMT 3 Server: Apache/2.0.54 (Debian GNU/Linux) mod_jk/1.2.15 mod_python/3.1.3 Python/2.3.5 mod_ssl/2.0.54 OpenSSL/0.9.7e 4 Set-Cookie: JSESSIONID=46EB32A9D7568A1F0222E94068AA0482; Path=/webfilter 5 Content-Length: 1434 6 Keep-Alive: timeout=15, max=100 7 Connection: Keep-Alive 8 Content-Type: text/html;charset=UTF-8 200 OK If I double-click on the http://192.168.1.1/webfilter/blockpage?nonce=e2c01ae50a9a2c79&tid=10 I do get the web filter warning page, so the resulting HTML is ok (ie. no Javascript which NetSurf doesn't like). It looks like NetSurf doesn't like the 307 temporary redirect. Paul -- Using, programming and promoting RISC OS - the most productive computer system in the world. Check it out now, and change your view of computers!! To reply/email, visit http://www.riscos.org/feedback/ Better to remain silent and be thought a fool than to speak and remove all doubt.
