WordPress.org

Forums

Question about HTTP status header (5 posts)

  1. Reaper-X
    Member
    Posted 9 years ago #

    I have question about http status header, and that's because i just found out that my site status header always returning 302 status header instead of 200, and the 301 redirect also doesnt work and always return the 302 status header, but this problem only occur at my site not at the other site (i've also check other site like, tamba2, wordpress.com, wordpress.org, etc and always returning the correct status header)

    here's the status header from my site reaper-x.com :

    HTTP/1.1 302 Moved Temporarily
    Content-Length: 0
    Location: /?ABCDEFGH

    and here's the result from my test site reaper.gig4free.com :

    HTTP/1.1 200 OK
    Date: Sun, 20 Aug 2006 07:22:47 GMT
    Server: Apache/1.3.36 (Unix) mod_layout/3.2.1 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 mod_ssl/2.8.27 OpenSSL/0.9.7f PHP-CGI/0.1b
    X-Powered-By: ModLayout/3.2.1
    Connection: close
    Content-Type: text/html

    Thanks in advance and sorry for my bad english

  2. Mark Jaquith
    WordPress Lead Dev
    Posted 9 years ago #

    I'd talk to your web host... that's very strange behavior.

  3. Reaper-X
    Member
    Posted 9 years ago #

    actually i've emailed my web hosting (godaddy) because i dont think i'll get answers here .. lol, and still waiting for a reply ... anyway thanks alot ;)

  4. flanker
    Member
    Posted 8 years ago #

    Hi Reaper-X. Did you get a satisfactory response from GoDaddy regarding this issue? All of a sudden, I'm experiencing the exact same problem. I haven't changed anything in months, but suddenly everything returns a 302.

  5. flanker
    Member
    Posted 8 years ago #

    Replying here for anyone who stumbles across this. After trying to convince me several times that the problem was due to something I had done (firewall, cookies, coding error), GoDaddy escalated the problem to their real technical support guys who immediately responded saying that there was an issue with a firewall *on my server.* They offered to move me to a different server, which I accepted, and a DNS update later, I'm back to normal.

    Bottom line: You need to get past that first-line of defense at GoDaddy support to the people who know how to fix this.

Topic Closed

This topic has been closed to new replies.

About this Topic