Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Http response headers stripped by ATT 3G/4G

Oct 20, 2012 11:09PM PDT

When accessing certain websites by ATT 3g/4g tethered to a PC a page full of seemingly random characters is returned instead of normal page content. This has been occurring for approximately 2 months and has been reported to ATT and affected websites (Hotwire, New York Daily News, and CNET). ATT states that it's not their problem. Hotwire and NY Daily have made changes to adapt to the situation CNET has not. I submitted a support request to CNET (incident # 120919-000146) on 9-19-2012 but have not recieved a response. I have corresponded with others having these problems on ATT forums and they are much more technically aware than I. This is a link to that discussion. http://forums.att.com/t5/Data-Messaging-Features-Internet/3G-proxy-wnsnet-attws-com-strips-HTTP-response-headers/td-p/3294533 . Please excuse my lack of knowledge and terminology in these areas as I am just a user, not a tech.

Discussion is locked

- Collapse -
". Changing the order in the headers solved the issue."
Oct 21, 2012 4:58PM PDT

It appears that the web site has to know this and workaround it.

It's sort of like that GoDaddy DNS blackout issue. Could confuse folk that didn't know.
Bob

- Collapse -
Shouldn't have to workaround
Oct 21, 2012 10:44PM PDT

If ATT would take ownership of this problem it wouldn't be a problem. They made some change in programming around 8-25-2012 but won't acknowledge the effect. I can't fault CNET for the problem. I am just trying to let them know that there is a problem and apparently a workaround exists. I usually am able to access the CNET homepage but review pages are often scrambled. There are probably so few people accessing their site by use of 3G/4G tethered computers that it isn't worth the resources to address the situation. Can't say I didn't try.

- Collapse -
It's like a friend I know.
Oct 22, 2012 3:32PM PDT

They used some protocol that we warned them that needed some work. They tested it and later it broke.

So whose fault is it? You could say it's the network this traveled on but we looked at it and sure enough it's the issue we warned about. And no, it was not http headers.

Said friend is still demanding they fix their network. (never going to happen.)
Bob