-
Lynx FAQ :
Trouble spots :
Lynx 2.8.4 error 400 bad reguest malformed syntax :
Check ~/.mailcap for broken entries
- Check the aforementioned file for broken entries -- in my case, lynx generated broken Accept HTTP headers which caused the web-server to answer with a
400 answer. Netscape web-servers exhibit this behaviour (e.g. www.cnn.com). The entries in .mailcap should not contain non-ASCII characters.
saschaATschumannDOTcx
- [Append to This Answer]
Previous
Check your ~/.mailcap and ~/.mime.types files. In my case, a broken entry containing non-ASCII characters caused 400 replies. Netscape web-servers reject those Accept: headers which are caused by such entries.
Next
New Item
This document is: http://lynx.isc.org/cgi-bin/fom?file=128
[Search]
[Appearance]
[Show Expert Edit Commands]
This is a Faq-O-Matic 2.711.
FAQ Admin|Mailing list