[Lynx-dev] share your information with this source, was Amazon broken (HTTP 204)

[Karen Lewellen]

Hi all
I just phoned Amazon again.
I am placing below an email from a supervisor involved with their tech 
efforts to repair this problem.
If you can, contact him at the address he provides as the reply to here.
Share that you got the address from me in an effort to give tech support a 
variety of examples from different platforms using lynx.
here is the communication,
From address@hidden Fri Jun 13 20:24:06 2014
Date: Sat, 14 Jun 2014 00:24:05 +0000
From: Amazon.com <address@hidden>
Reply-To: "address@hidden" <address@hidden>
To: "address@hidden" <address@hidden>
Subject: A Message from Amazon Customer Service - Re: Account Access

Amazon
Your Account Amazon.com
Message From Customer Service
Hi Karen,

A colleague let me know you called in asking for an update from me.
From our last conversation, I was under the impression you didn't
want to be contacted with just a "we're still looking into this"
update. I'm sorry if I misunderstood.

Could you please try using the links on our amazon.com/access page
again? If they still don't work, could you please let me know the
date/time you attempt? Ideally, they'll work for you, but if not
we'll be generating a fresh example for our team to work with.

Best regards,
Ben B.
Did I solve your problem?
Yes?? No

Your feedback is helping us build Earth's Most Customer-Centric
Company.

Thank you.
Amazon.com[r.html?R=3KCHNE60K98UK&C=3GG4DES2VDURU&H=ZTAMO4HFIW3NDDNOPK4FLHCVFIYA&T=E&U
=http%3A%2F%2Fimages.amazon.com%2Fimages%2FG%2F01%2Fnav%2Ftransp.gif]

Pass this on widely,
Kare


On Mon, 30 Jun 2014, 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.
>
> * 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
>
> _______________________________________________
> Lynx-dev mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/lynx-dev