Walter Ian Kaye <[EMAIL PROTECTED]> wrote:

> This might explain it:

[ problem with blocking Lynx User-Agent header ]

That was exactly it. The possibility of the Lynx user-agent header being
blocked and not those of elinks and w3m seemed so remote to me that I did
not even consider it. If this is becoming a trend with hand-fisted
administrators to block on user-agent lines with libwww in them, then
maybe we should think about changing the default value in Lynx?


Thanks,

Morten




_______________________________________________
Lynx-dev mailing list
[EMAIL PROTECTED]
http://lists.nongnu.org/mailman/listinfo/lynx-dev

Reply via email to