prebid-server-java
prebid-server-java copied to clipboard
prebid
WARN 7 --- Invalid request format: request.ext.prebid.aliases.freewheelssp refers to unknown bidder: freewheel-ssp
As the title says, we have a following error that occurs when a request is sent to our server instance Invalid request format: request.ext.prebid.aliases.freewheelssp refers to unknown bidder: freewheel-ssp
However, we did not define this alias anywhere explicitly. Instead, it seems like there is a default request that is being sent to our server. We have tried to override these parameters through s2sConfig and by configuring some server yaml files, but nothing helps. We have checked all the configurations of our server and we cannot locate where this request is actually made. Also, tried setting a default-request path to try to override this one, but that did not help either.
Did you, by any chance, encounter this and do you have any suggestions on how to change this request? We cannot proceed with our implementation until we fix these bugs.
Below I provide screenshots of the files, configurations, etc.
freewheelssp configuration (added alias here after the error appeared and set it to disabled to see if it will work):
Tried defining freewheel-ssp, but did not help:
Tried defining default request, both in application.yaml and prebid-config.yaml (for testing purposes only):
We have only this alias in s2sConfig:
Do you have any idea why is this happening and how to access this, what it seems like, a default request that is giving these errors? Thanks
Hello, @dzesm . This is weird, as PBS doesn't use a default request unless you explicitly enable it. So unless you provided the default request, nothing should be added to your incoming request.
Are you using stored requests by any chance? As this is the first thing that comes to mind.
Another thing that I can recommend is to make sure that nothing else on your page modifies the s2s config and that PBS is getting the request without freewheel alias.
Hello, @dzesm Do you still have this issue or we can close this one?
@dzesm Closing this issue due to no activity. If you have any other questions, feel free to reopen it.