Skip to content
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

Submit Brightcom Bid Adapter #3614

Merged
merged 3 commits into from
Mar 8, 2019
Merged

Conversation

vyatsun
Copy link
Contributor

@vyatsun vyatsun commented Mar 5, 2019

Type of change

  • Bugfix
  • Feature
  • New bidder adapter
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Does this change affect user-facing APIs or examples documented on http://prebid.org?
  • Other

Description of change

  • test parameters for validating bids
{
  bidder:  'brightcom',
  params: {
    publisherId: 2141020
  }
}

Be sure to test the integration with your adserver using the Hello World sample page.

For any changes that affect user-facing APIs or example code documented on http://prebid.org, please provide:

Copy link
Collaborator

@jsnellbaker jsnellbaker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @vyatsun

While trying to test the adapter, I was encountering a CORS error when it was requesting the bids.

Below is a copy of the error message for reference:

Access to XMLHttpRequest at 'https://brightcombid.marphezis.com/hb' from origin 'http://test.localhost:9999' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Can you please take a look? If you need any additional details on the request or payload, please let me know.

@vyatsun
Copy link
Contributor Author

vyatsun commented Mar 7, 2019

Hi @jsnellbaker

Could you please try again, and make sure you're sending the 'Origin' and 'User-Agent' headers?

If it still doesn't work for you, please share the request details.

Copy link
Collaborator

@jsnellbaker jsnellbaker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @vyatsun

Thanks for making the update; I can verify that the adapter is successfully returning a bid now with the test params and everything looked good from that perspective.

However there is another item that should be ideally addressed before we merge the adapter. I've made a note below at the relevant area in the code. Can you please take a look when possible?


function buildRequests(bidReqs, bidderRequest) {
try {
const loc = utils.getTopWindowLocation();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This function is eventually going to be deprecated, so it shouldn't be used if possible.

We have setup an alternative feature with this type of information that can be used instead. The associated domain data can be accessed via the bidderRequest.refererInfoobject.

The following page provides some additional details on the object and its data points if you want to review further:
http://prebid.org/dev-docs/bidder-adaptor.html#referrers

@vyatsun
Copy link
Contributor Author

vyatsun commented Mar 8, 2019

Hi @jsnellbaker

I've removed the utils.getTopWindowLocation() call.

@jsnellbaker
Copy link
Collaborator

Hi @vyatsun Thanks for making the updates; LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants