Almost no ads are shown: Change Android Adview response from HTTP protocol to HTTPS

300 views
Skip to first unread message

in...@koeck.nl

unread,
Oct 24, 2015, 5:08:17 PM10/24/15
to Google Mobile Ads SDK Developers
Dear Sir/Madam,

How and where can I change the HTTP protocol of the response I get for my adview from HTTP to HTTPS?
This to enable my adview to show the ads.
When I use my own Admob ads everything works fine. Also when setting up a mediation of Admob in my DFP Small Business server everything is fine as well.
But there are almost no ads when I connect the app with the DFP server of a media agency. The majority of their inventory consists of third party networks who apparently still send ads over HTTP.
Changing the HTTP protocol of the response of the ad request will make it possible to show the ads (based on the big help from Vu Chau).

Below is the error I receive in the logcat:

10-23 19:56:15.813 18492-18492/com.koeck.verdienapp W/chromium: [WARNING:web_contents_impl.cc(2990)] https://pubads.g.doubleclick.net ran insecure content from http://ib.adnxs.com/ttj?id=4433225&size=300x250&referrer=com.koeck.android&cb=774743058&psa=false&position=above

10-23 19:56:15.823 18492-18492/com.koeck.verdienapp W/chromium: [WARNING:web_contents_impl.cc(2990)] https://pubads.g.doubleclick.net ran insecure content from http://ib.adnxs.com/ttj?id=4433225&size=300x250&referrer=com.koeck.android&cb=774743058&psa=false&position=above

10-23 19:56:15.823 18492-18492/com.koeck.verdienapp W/Ads: JS: Mixed Content: The page at 'https://pubads.g.doubleclick.net/gampad/ads' was loaded over HTTPS, but requested an insecure script


Thanks for taking the time to read my question.

Kind regards,
Rogier van den Brink
Message has been deleted

Vu Chau (MobileAds SDK Team)

unread,
Oct 26, 2015, 5:10:01 PM10/26/15
to Google Mobile Ads SDK Developers
Hi Rogier,

As I explained, responses from the media agency (ib.adnxs.com) and its third-party networks have to be served over HTTPS as well for mediation to succeed.  The team does not have knowledge of this network setup so we aren't able to provide further insights.  Apparently you could proxy/reroute the traffic and force HTTPS for the responses, but I have not tested this setup.  The networks with which you are custom-mediating will have to turn on HTTPS. 

Let us know what you find,

Vu Chau
Mobile Ads SDK Team

koeck nl

unread,
Oct 27, 2015, 9:21:34 AM10/27/15
to google-adm...@googlegroups.com

Hi Vu Chau,

Thanks again for your answer.
We have found a solution with some adjustments on the adserver from our media agency.

Best regards,
Rogier

Op 26 okt. 2015 22:10 schreef "Vu Chau (MobileAds SDK Team)" <mobileadssd...@google.com>:
--

---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/3SV0FEOF9Lg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.
To post to this group, send email to google-adm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Message has been deleted

Austin Bai

unread,
Jun 15, 2016, 7:42:26 AM6/15/16
to Google Mobile Ads SDK Developers
Hi Vu Chau,

This post is really helpful as I am facing the same issue during Android SDK integration. I am currently adding SDKless mediation ad sources to my waterfall but 80% of the delivered ads are not rendered. I have asked the mediation partner to set up both HTTP and HTTPS test campaigns but I am able to render both in my app. 

Can I clarify with you that if the HTTP URL call is totally blocked in Android SDK? If it is not 100% blocked, what are the criteria to block HTTP URL calls? 

Best regards,
Austin 

Vu Chau (Mobile Ads SDK Team)

unread,
Jun 15, 2016, 8:47:35 PM6/15/16
to Google Mobile Ads SDK Developers
Hi Austin,

I don't have a definitive response for this, since the heuristics that handle mixed content are at the level of the Android SDK (as opposed to the Mobile Ads SDK).  The Mobile Ads SDK uses a WebView to process and render all the ad traffic, so if it receives a batch of mixed content, it will apply the latest heuristics that ship with the latest WebView APK.  That is out of scope for our team.

If, in your release, you notice a fair amount of insecure HTTP traffic coming in to your app, the WebView has a mode called MIXED_CONTENT_COMPATIBILITY_MODE that you can utilize.

Vu Chau
Mobile Ads SDK Team

Reply all
Reply to author
Forward
0 new messages