-
Notifications
You must be signed in to change notification settings - Fork 737
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
New Adapter: Nativo #3790
base: master
Are you sure you want to change the base?
New Adapter: Nativo #3790
Conversation
Code coverage summaryNote:
nativoRefer here for heat map coverage report
|
@onkarvhanumante Is there any ETA for reviewing this PR? |
@rafataveira PR tests are failing due to file miss format. Requesting to format files
|
@rafataveira Does this bidder supports |
@@ -0,0 +1,19 @@ | |||
endpoint: "https://exchange.postrelease.com/esi?ntv_epid=7" | |||
maintainer: | |||
email: "prebiddev@nativo.com" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've sent an email to this address to confirm it is correct. Please respond to the email with a "received" message.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is correct. I've just replied to the email.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mail confirmed
static/bidder-params/nativo.json
Outdated
"title": "Nativo Adapter Params", | ||
"description": "A schema which validates params accepted by the Nativo adapter", | ||
"type": "object", | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NIP, please delete white line
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
adapters/nativo/nativo_test.go
Outdated
|
||
func TestBidderNativo(t *testing.T) { | ||
bidder, buildErr := Builder(openrtb_ext.BidderNativo, config.Adapter{ | ||
Endpoint: "https://foo.io/?src=prebid"}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is it "https://foo.io/?src=prebid" ?
It should be endpoint from yaml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
@@ -0,0 +1,19 @@ | |||
endpoint: "https://exchange.postrelease.com/esi?ntv_epid=7" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"esi?ntv_epid=7" does not look fine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is correct, that's the url to our exchange server, in this case, prebid server.
@onkarvhanumante I will review all comments and make the changes accordingly. |
Code coverage summaryNote:
nativoRefer here for heat map coverage report
|
Code coverage summaryNote:
nativoRefer here for heat map coverage report
|
I see this 200 response as well but it is supposed to redirect (302) to the PBS setuid endpoint which is specified in your |
@bsardo This is the result of the redirect I get: |
Hi @rafataveira, I suggest testing your user sync with localhost so that your bidder is known and so that you can ensure your server redirects to the setuid endpoint of the PBS host, which in this case will be the localhost setuid endpoint. Start this process by first hitting the localhost PBS cookie sync endpoint: |
Code coverage summaryNote:
nativoRefer here for heat map coverage report
|
I found the issue with the double quotes on userMacro. Now it should work as expected. |
@rafataveira we're still seeing an issue with the user sync. Your server is responding with a 200. Since you've classified this user sync as type redirect, your server should be responding with a 302 redirect to the url defined in the |
@bsardo I couldn't reproduce this behaviour. As you can see, our server responds with 302 and correctly redirects to the URL defined in the
|
@onkarvhanumante @przemkaczmarek @bsardo, is the cookie sync URL the only thing preventing you from approving this PR? We have some clients waiting for the GO version to go live for quite some time. Could you please go ahead and approve it? The cookie sync URL is the same as prebid-server-java and other partners, and it is working as expected. |
Hi @rafataveira, yes the user sync is the only thing holding this up. We tried the URL you provided as well and it is still not working for me or Peter and we are based in the US and Poland respectively in case this is a geographic region issue. We are still seeing a 200 instead of a 302 redirect. This issue needs to be resolved before merging this PR as is unless you want to break the user sync functionality out into a separate PR so that the rest of this can be merged now. At this point, I am leaving the user sync investigation up to you though I will triple check with another team member that the 200 issue is occurring and report back later today. |
@bsardo I see what is happening to your validation. This is a production cookie sync URL which has different kinds of internal validations to avoid fraud and won't redirect if a possible fraud is detected. It works for me because I am in a VPN environment. This has nothing to do with our GO version adapter at all. If this is still a blocker for you to approve this PR, (even though it is not a problem) we can remove it from this PR and also, change our validation for Prebid Server to always redirect. Let me know what you recommend. |
@rafataveira we're required to verify the user sync endpoints works. Can you either provide details on how to construct a request so that it is not flagged by your servers as potential fraud or change your server validations so that the URL generated by the cookie sync endpoint always results in a redirect? I'll leave that decision to you at this time as I'm not aware of how your validation works. |
@bsardo we have pushed a fix for the redirect validation. Can you please validate and if all looks good can we merge the PR? |
@bsardo can we get an update on the cookie sync validation ? |
Code coverage summaryNote:
nativoRefer here for heat map coverage report
|
Hi @aparekh-nativo, @rafataveira tests are failing and your PR branch does not run because you have some incorrect package references after merging with master. All package imports should reference v3 instead of v2. It looks like the offending files are |
Code coverage summaryNote:
nativoRefer here for heat map coverage report
|
Code coverage summaryNote:
nativoRefer here for heat map coverage report
|
@bsardo The merge issue and test failures are fixed. Could you please go ahead and merge it? |
Hi @rafataveira, now I see the redirect working but the user id macro Your server appears to just be echoing whatever I send as |
No description provided.