Conversion Not Working

[seandly]

Hi,

 

trying to figure out why conversion is not working, i’m seeing the following in tamper:

 

Set-Cookie=_OXLIA[13]=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/

%5FOXLIA%5B13%5D=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/

****

…the date shows 1970. thinking maybe this is the cause.

 

can’t seem to figure out why it’s saying this date and where to fix this.

 

thanks

 

[andrewatfornax]

That suggests Revive Adserver is deliberately trying to delete a cookie by setting the date in the past. However, I'd have to know more about when you're seeing this to try to understand it...

[Christiane]

I have the same problem:

HttpResponseProxy{HTTP/1.1 200 OK [Server: nginx/1.4.6 (Ubuntu), Date: Mon, 12 Dec 2016 13:09:02 GMT, Content-Type: image/gif, Transfer-Encoding: chunked, Connection: keep-alive, Set-Cookie: _OXLCA[6]=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/, Set-Cookie: %5FOXLCA%5B6%5D=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/, Pragma: no-cache, Cache-Control: no-cache, no-store, must-revalidate, Expires: 0, Access-Control-Allow-Origin: *, P3P: CP="CUR ADM OUR NOR STA NID", Set-Cookie: OXLCA=6.ui00e7-4; expires=Tue, 12-Dec-2017 13:09:02 GMT; Max-Age=31536000; path=/] ResponseEntityProxy{[Content-Type: image/gif,Chunked: true]}}

[andrewatfornax]

Do things work differently if you don't have a reverse proxy in front of Revive Adserver?

Just wondering if this is something to do with the proxy, rather than Revive Adserver (or if there's an issue with Revive Adserver when used with a reverse proxy)...