-
Notifications
You must be signed in to change notification settings - Fork 735
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
Stop hard-failing on unknown imp.ext values #3735
Comments
One option might be adding it to the list of reserved keys but that is an inclusive list: prebid-server/openrtb_ext/bidders.go Line 251 in 7702a78
|
I suppose that would be faster, but I'd like to fix this once and for all |
This is a high priority because imp.ext.igs is now a thing. |
Hey, gentle bump |
Should be in PBS-Java this week. @bsardo - is this in the queue for PBS-Go? |
Released with PBS-Java 3.9. Discussed in committee - this is on the radar for PBS-Go. |
One of the RTD modules starting putting data on imp.ext, and PBS is choking on it.
This isn't right... imp.ext should be for everyone to use... PBS shouldn't assume that every value in that ext must be a bidder to the point where it hardfails.
Instead, if an unknown value in imp.ext is found, PBS should do the following:
Note: we already make exceptions for many imp.ext values: ae, all, context, data, general, gpid, prebid, skadn, and tid. We can keep these special cases to reduce the number of warnings emitted.
Test cases:
The text was updated successfully, but these errors were encountered: