You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Safari isn't respecting the response headers for the Audience Network bidder so it's caching some bid requests. This could be only when multiple requests go out before responses come back for any but it's specific to Safari.
Are you able to add a cachebuster param to our endpoint? Something like this:
'&cb=${random()}'
Steps to reproduce
Reproducible in Safari mobile web.
Test page
Reach out if needed.
Expected results
All bids should be unique.
Actual results
Seeing the same bidid used over and over because safari is caching requests.
Hi John, the caching problem you've experienced in Safari has been reported to Apple but in the meantime I'll add your excellent suggestion of a cachebuster to workaround this until an upstream fix is available.
Type of issue
Bug
Description
Safari isn't respecting the response headers for the Audience Network bidder so it's caching some bid requests. This could be only when multiple requests go out before responses come back for any but it's specific to Safari.
Are you able to add a cachebuster param to our endpoint? Something like this:
'&cb=${random()}'
Steps to reproduce
Reproducible in Safari mobile web.
Test page
Reach out if needed.
Expected results
All bids should be unique.
Actual results
Seeing the same bidid used over and over because safari is caching requests.
Platform details
Safari mobile web
Other information
N/A
cc @lovell
The text was updated successfully, but these errors were encountered: