[Lynx-dev] Amazon broken (HTTP 204)

[Aahz Maruch]

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.

* The other problem is that Amazon's main login claims that Lynx isn't
using cookies (this has been going on for years and is why I just login
through the mobile/accessibility subsite):

https://www.amazon.com/ap/signin?_encoding=UTF8&openid.assoc_handle=usflex&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.mode=checkid_setup&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.ns.pape=http%3A%2F%2Fspecs.openid.net%2Fextensions%2Fpape%2F1.0&openid.pape.max_auth_age=0&openid.return_to=https%3A%2F%2Fwww.amazon.com%2Fgp%2Fcss%2Fhomepage.html%3Fie%3DUTF8%26ref_%3Dgno_yam_ya

[...]  Oh, futz, Amazon's playing games with User-Agent, when I set mine
to "Mozilla/5.0" it works.  (You may substitute something stronger for
"futz".)

Figure I'll send this anyway in case it helps someone else.  :-(  I
haven't seen broken cookie behavior based on User-Agent before.

Thanks,
Aahz