-
Notifications
You must be signed in to change notification settings - Fork 748
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support GET on the /vtrack endpoint #3629
Comments
Discussed in committee. There was concern that this may increase the prevalence of cross datacenter reads. In the end the prevalence of that scenario probably wouldn't increase as a result of this, but still, added the |
@bretg it's my understanding that this has been recently discussed in the CTV meeting. Have we made any progress on this? |
Close - we discussed the GET endpoint in the CTV committee, not the /vtrack endpoint. |
Discussed in committee. Marking it as ready for dev. The committee doesn't have any concerns and the |
We built the the /vtrack endpoint in #1015
The usage pattern is that Prebid.js users set this config:
Turns out there's a wrinkle where in the outstream scenario, Prebid.js is now using
cache.url
to retrieve the creative. This has been the case for a long time but I never noticed it until recently. The end result is that there are requests to /vtrack failing because they're GETs with&uuid=
appended.Changing Prebid.js is difficult, so the proposal is to change Prebid Server at least as an initial solution:
uuid
parameter. If there's nouuid
, return 404.ch
parameter, this is a "cache host url". See Prebid Cache Cross Data Center Lookup #1620uuid
parameter, call PBC to retrieve that uuid.The text was updated successfully, but these errors were encountered: