On Mon, Jun 30, 2014 at 10:01:36AM -0700, Aahz Maruch wrote:
Howdy,
Amazon broke Lynx about three months ago; I tried chatting with them
today, but they won't even give me a bug number (although they claim
they'll forward a message to their technical team). Because "links"
works with Amazon, I figured I'd try asking y'all whether there's
something you can do.
There are actually two problems:
* The newer problem is that using Amazon's "mobile/accessibility"
subsite causes an HTTP 204 on this URL:
https://www.amazon.com/gp/aw/ya?ref_=aw_bottom_links_ya
It looks like wget has the same problem.
Perhaps this is also user-agent?
(I'm in the middle of upgrading a server, otherwise would test this).
Figure I'll send this anyway in case it helps someone else. :-( I
haven't seen broken cookie behavior based on User-Agent before.
When someone sets out to intentionally break their web server, it can have lots
of symptoms.
--
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net