The venerable http://washingtonpost.com is sending its mobile version of
its front page to ssl enabled lynx with a 301 Moved Permanently.
It appears the server redirect to http://mobile.washingtonpost.com triggers
consistently if lynx is built with ssl afaict, but the regular page is served
to non-ssl built lynx. I don't know for sure if this is the only variable, but
it seems so:
2.8.5dev.8 and dev.15 no ssl, no 301, regular page
2.8.6dev.17 and 18 ssl, mobile page
2.8.6rel.1 ssl, mobile page
2.8.7dev.1 no ssl, no 301, regular page
2.8.7dev.4 ssl, mobile page
Anyone else seeing this?
__Stef
http://caunter.ca/contact.html
_______________________________________________
Lynx-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lynx-dev
