Replies: 3 comments 10 replies
-
|
Maybe you aren't setting the User-Agent header field? If you could post the significantly different data you get, someone might be able to figure it out. |
Beta Was this translation helpful? Give feedback.
-
|
Do you have an example of the difference? |
Beta Was this translation helpful? Give feedback.
-
|
I'm experiencing inconsistent results when accessing the API from different clients. Specifically, I'm trying to retrieve the first element from the "periods" array in the response. When I call the API from my Java application, I get one timestamp, but when using Postman to make the exact same request, I receive a different timestamp - for example, startTime="2025-06-04T00:00:00-07:00" - which differs by one hour from my Java results. In some cases, I've observed differences of 7-8 hours between different clients.
|
Beta Was this translation helpful? Give feedback.
-
|
Sounds like you're getting some caching differences between the sources. The 1 hour difference is easily explained that way-- Postman gets an earlier version and its CDN node caches it for 45 minutes while the hit from your workplace/home gets fresh data. It's expected behavior and isn't a problem in normal operation. You can check the Cache-Control headers to see how long the CDN node is going to keep the page data before it'll fetch from the origin again. 8 hour difference shouldn't happen, though. Can you post some sample headers for requests that contain stale data that is more than an hour old? I'm also assuming you're considering timezone differences between locations/clients. If you're getting responses in UTC vs PDT, that would explain the 7 hour "difference." |
Beta Was this translation helpful? Give feedback.
-
|
Is the updateTime different between the requests? That time is when the forecast grid data are updated. |
Beta Was this translation helpful? Give feedback.
-
|
Not the OP but I'm currently seeing a 9-hour forecast returned to my server. WFO/x,y/forecast response headers:
WFO/x,y response headers
WFO/x,y/forecast/hourly response headers:
|
Beta Was this translation helpful? Give feedback.
-
|
It appears its being cached at the edge server with the request, differ the user-agent or add a query string param t={epoch}. The user agent difference is most likely why you are seeing differences from PostMan and your code, however, you should try the query string option first.
From: pshijie ***@***.***>
Sent: Friday, June 6, 2025 6:31 AM
To: weather-gov/api ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [weather-gov/api] Issue with Inconsistent Responses from API (Discussion #824)
I'm experiencing inconsistent responses when calling the Weather.gov API endpoint https://api.weather.gov/gridpoints/LOX/160,43/forecast/hourly from my Java application compared to Postman requests.
When I make a request using Postman, I receive the expected weather forecast data. However, when I call the same endpoint with identical parameters from my Java application, the response differs significantly.
Here's the code I'm using to make the API request:
HttpResponse response = HttpRequest.get(url)
.timeout(5000)
.header("Accept", "application/json")
.execute();
I've already tried:
* Adding cache control headers to prevent caching
* Verifying the status code is 200 for both requests
Is there any known issue with the API that could cause different responses based on the client making the request? Are there specific headers or parameters required when accessing the API programmatically that might not be needed when using Postman?
Any guidance on how to ensure consistent responses between Postman and programmatic API calls would be greatly appreciated.
Thank you!
—
Reply to this email directly, view it on GitHub<#824>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADJHCGY7W7HRHEDQGIT3ZGD3CGJYRAVCNFSM6AAAAAB6YCTR7WVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYGQZDIOJTGY>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>
|
Beta Was this translation helpful? Give feedback.
-
|
It's been a while since I looked, but cache busting using additional parameters is disabled on the API endpoints. |
Beta Was this translation helpful? Give feedback.
-
|
While the forecast data hasn't updated between requests the start time has moved forward each hour. As currently designed the cache in the CDN is not always updating until the forecast grids are updated and that can be up to 12 hours between forecast updates. |
Beta Was this translation helpful? Give feedback.
-
|
I'm now consistently seeing an older forecast pulled from my server vs. what I get at home on my browser - so I'm assuming that there's an issue with the cache that my server is hitting. Is this something to bring up here or should I let NCO Ops know? Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
By older forecast do you see an older updateTime or an earlier first hour but same updateTime? |
Beta Was this translation helpful? Give feedback.
-
|
Here's what I have on the web server:
and this is what I pull from my web browser:
So it's the latter - same update time, but different generation times. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Yes, that's an older response but not actually older forecast data. We are looking at how to better handle that cache in the CDN since the response changes each hour. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm experiencing inconsistent responses when calling the Weather.gov API endpoint https://api.weather.gov/gridpoints/LOX/160,43/forecast/hourly from my Java application compared to Postman requests.
When I make a request using Postman, I receive the expected weather forecast data. However, when I call the same endpoint with identical parameters from my Java application, the response differs significantly.
Here's the code I'm using to make the API request:
I've already tried:
Is there any known issue with the API that could cause different responses based on the client making the request? Are there specific headers or parameters required when accessing the API programmatically that might not be needed when using Postman?
Any guidance on how to ensure consistent responses between Postman and programmatic API calls would be greatly appreciated.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions