Forum Moderators: martinibuster

Message Too Old, No Replies

HTTP 400 - Bad Request

after inserting new ad code

         

Hobbs

11:30 am on May 11, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Right after inserting new ad code into a page on my server, requesting that page shows an error "HTTP 400 - Bad Request" within the AdSense iframe area. While all other pages are showing old ads fine.

Refreshing that page few minutes later shows the ad with no errors.

When generating ad code it tells you:
"Your AdSense unit has been saved. Changes may not appear for up to 10 minutes"

And that's fine, I used to see an empty space before till the ads start showing, but never an "HTTP 400 - Bad Request", is this a new bug?

marcel

11:41 am on May 11, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I had exactly the same problem yesterday, lasted about 15 minutes. Thought it may have something to do with some A/B testing I had set up. (first ad unit showed up fine, the second gave the error)

Hobbs

12:28 pm on May 11, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Was your ad code too newly generated?

I just don't like my visitors seeing a box with an error on my pages, even for few minutes, that's a lot of visitors for my site.

marcel

4:41 pm on May 11, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Was your ad code too newly generated?

Sorry, forgot to add that... Yes, I had just created two new ad units, the first showed up fine, but the second one gave me the error.

It took me a little while to notice, as the error does not show in firefox (just a blank area). I opened up IE in case it was a caching error and then saw the Error message.

Hobbs

5:02 pm on May 11, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Same here, I was unable to see the error in FireFox
It only showed in IE

If you do a view source inside the iframe, and Google any part of that html code like e.g. "for the href, we need a valid URL to the domain" the first 2 results in the serps are related to script injection! Which sent me on a fool's errand till I calmed down and realized on my own that it was just the MS error 400 :-)

[edited by: Hobbs at 5:02 pm (utc) on May 11, 2008]

thegreatpretender

2:02 am on May 12, 2008 (gmt 0)

10+ Year Member



I have the same problem. I was trying to replace an old unit with a new one and got the error. I checked manage ads in my account and noticed that the status of the ad was "new" and not "active" as others have. So I put the old one back and let the new one became active before putting it back again.