Note that there are some explanatory texts on larger screens.

plurals
  1. POPHP Port 80 redirect + 'argv'
    primarykey
    data
    text
    <p>Here is the output from Live Http Headers:</p> <pre><code>http://www.sitename.com/loginapplet.ws?mod=main&amp;dest=maintenance.php GET /loginapplet.ws?mod=main&amp;dest=maintenance.php HTTP/1.1 Host: www.sitename.com User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip, deflate Referer: http://www.sitename.com/maintenance.php?COLLCC=3673562052&amp; Cookie: __utma=101585024.21651761.1342192562.1342694644.1342697578.76; __utmz=101585024.1342192562.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=83ce1589fb215697fb3cba35531f133f; __utmc=101585024; __utmb=101585024.2.10.1342697578 DNT: 1 Connection: keep-alive HTTP/1.1 302 OK Connection: Keep-Alive Location: http://www.sitename.com/loginapplet.ws?COLLCC=3673562052&amp;mod=main&amp; dest=maintenance.php X-Antivirus: avast! 4 X-Antivirus-Status: Clean </code></pre> <p>For clarity, the problem is the addition of the <code>?COLLCC=</code> on to the query string. I have done some googling and found other URLs that have this string appended to them but none of them were of any help.</p> <p>Does anyone have any idea what could be causing this? My server doesn't even use Avast, and also, nothing in my application is causing this redirect internally..</p> <p>The problems seems to have resolved itself. I'm not sure why apache didn't suffer this problem like nginx did but I'm going to go ahead and guess that it's a problem with nginx that needs reviewing.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload