Expand my Community achievements bar.

SOLVED

Troubleshoot problems with the Visual Experience Composer in Adobe Target :Enhanced Visual Experience Composer won't load on secure pages on my site.

Avatar

Level 2

In our application, we are facing Composer won't load on secure pages on my site issue and planning to whitelist below ip address.54.80.158.92

•54.204.197.253

•54.72.64.46
•54.72.56.50
•54.199.198.109
•54.199.241.57


Our Security Architecture reviewed these ip's and they have requested us to narrow it down to source/destination/protocol/port for a set time frame.

Could you please help me on this.

Reference:https://marketing.adobe.com/resources/help/en_US/target/target/r_troubleshoot_composer.html

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hi Naga,

The Enhanced Experience Composer will make calls with paths that will match the page you are loading in the EEC. For example if you are loading this page in the EEC:

https://DOMAIN/folder1/folder2/file.html

The the referrer from the EEC will show up in your logs like so:

https://**-proxy.adobemc.com/folder1/folder2/file.html

The ** portion will vary by region.

For protocol and port it will match the protocol that you use in the url you enter. So in the case you've described it will be https and the related port of 443.

Here is a sample of what the server logs will look like when the EEC has made a request to your server:

54.199.241.57 - - [17/Jun/2016:09:55:30 -0600] "GET /js/library/select.js HTTP/1.1" 304 124 "https://apac-proxy.adobemc.com/games?vz_t=b&mboxEdit=1&mboxDisable=1&vz_url=https%3A%2F%2Fwww.gamesd..." "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0"

View solution in original post

1 Reply

Avatar

Correct answer by
Employee Advisor

Hi Naga,

The Enhanced Experience Composer will make calls with paths that will match the page you are loading in the EEC. For example if you are loading this page in the EEC:

https://DOMAIN/folder1/folder2/file.html

The the referrer from the EEC will show up in your logs like so:

https://**-proxy.adobemc.com/folder1/folder2/file.html

The ** portion will vary by region.

For protocol and port it will match the protocol that you use in the url you enter. So in the case you've described it will be https and the related port of 443.

Here is a sample of what the server logs will look like when the EEC has made a request to your server:

54.199.241.57 - - [17/Jun/2016:09:55:30 -0600] "GET /js/library/select.js HTTP/1.1" 304 124 "https://apac-proxy.adobemc.com/games?vz_t=b&mboxEdit=1&mboxDisable=1&vz_url=https%3A%2F%2Fwww.gamesd..." "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0"