After working for weeks, the API is now "caught" by Safari as having an unexpected colon

  • 3
  • Question
  • Updated 5 years ago
After working for weeks (probably months), the API is now "caught" by Safari as having an error, specifically,

The specific URL is "http://api.wunderground.com/api/KEY/f...

JSONlint.com parses the result as valid JSON but Safari is having a problem.
Photo of Steven Vance

Steven Vance

  • 2 Posts
  • 0 Reply Likes
  • confused

Posted 5 years ago

  • 3
Photo of Giacomo Bastianelli

Giacomo Bastianelli

  • 2 Posts
  • 0 Reply Likes
We do have the problem too, it looks it's at json format, while callback url parameter is set (by jquery), the json returned is not anymore included in a jsonp callback function.

As a result evaluating JSON fails in jquery.
Photo of Nalvio Cunha

Nalvio Cunha

  • 2 Posts
  • 0 Reply Likes
The same occurs with Chrome and Firefox.
This unexpected behavior is recent. There's some plan to solve this?
Photo of Giacomo Bastianelli

Giacomo Bastianelli

  • 2 Posts
  • 0 Reply Likes
Well according to me the problem is server side, as this is a jsonp case, the response cannot be "json" only but must be wrapped in a js function with name as the name passed in the callback parameter from the url.

Do you know how to escalate that issue to the wundergrood team as this is a blocking issue?
Photo of Nalvio Cunha

Nalvio Cunha

  • 2 Posts
  • 0 Reply Likes
I've sent a tweet to @weatherapi, there's another option?
Photo of Dave

Dave

  • 3 Posts
  • 0 Reply Likes
Seeing the issue here as well. Particularly bad timing as it disrupted a demo at CES.
We submitted a message via the Contact Support link on http://help.wunderground.com/
No response yet.
Photo of Dave

Dave

  • 3 Posts
  • 0 Reply Likes
Just received a response from support (in under an hour) - they're "working on the JSONP issue and will fix it as soon as possible."
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 122 Reply Likes
I'm sorry you've all experienced this bug. It has to do with how Akamai was dealing with our URL and caching, and the ?callback= was being dropped. It was erroneously identified as a cachebuster, not legitimate functionality. The fix is going out right now and should being functioning properly shortly.
Photo of Dave

Dave

  • 3 Posts
  • 0 Reply Likes
Verified that we're back up and running.
Thanks guys!
Photo of Steven Vance

Steven Vance

  • 2 Posts
  • 0 Reply Likes
Thanks! I verified that it's working, too!