Forums

    6 posts

  • avatar
    70 sounds
    134 posts
    "400 Bad Request"


    Hello all,

    I've been having an intermittent problem accessing the freesound website. I'm using Safari 4.0.4 on Mac OS 10.5.8

    I haven't been able to isolate the problem or reproduce it deliberately. I've observed it recurring intermittently over the last few months. This issue has only ever arisen for me on this website and no other. As it has recurred several times now, I thought I'd mention it here. This is what happens:

    Sometimes when I'm logged in, and I click on any freesound link or try to refresh any freesound page, I get a mostly blank page with

    400 Bad Request

    nginx/0.5.33

    Here's a screenshot from a few moments ago when I tried to access the freesound home page:

    http://spleencast.files.wordpress.com/2010/01/400-bad-request.png

    But then I try to access the freesound website through a proxy, and I can access the site just fine. On this occasion I had to access the site and log in through a proxy in order to post this message. I still get the "400 Bad Request" message when I try it in the usual way without a proxy, but as you see, when I use a proxy, I can browse and post to the site just fine.

    Is my IP being blocked or something? Do you think I've got an error with my browser or network settings? I could really use some help with this! Thank you. smile

  • avatar
    13 sounds
    237 posts


    Sounds like it might be a problem at your ISP. Perhaps their customer support can help.
    Have you tried temporarily setting a different DNS? (Dynamic Name Server)?

    I use Firefox on micro$oft Vista with Demon Internet and the occasional similar problems I've had (but not with freesound) have always been at Demons end, usually when they have issues with their DNS, or something reported as the "Authentication Server" whatever that is.

    Heaven in the sky is to die for, Heaven on earth is to live for.
  • avatar
    70 sounds
    134 posts


    strangely_gnarled
    Sounds like it might be a problem at your ISP. Perhaps their customer support can help.
    Have you tried temporarily setting a different DNS? (Dynamic Name Server)?

    I use Firefox on micro$oft Vista with Demon Internet and the occasional similar problems I've had (but not with freesound) have always been at Demons end, usually when they have issues with their DNS, or something reported as the "Authentication Server" whatever that is.

    Thank you, that's a good idea. I checked, and apparently my ISP only has one domain name server. So I looked up freesound's IP address and pasted that into my browser, and it resolved to the domain name just fine by itself. However, I still got the exact same "400 Bad Request" page. If I get the same result using both the IP address and the domain name, I'm thinking that this issue is something other than a domain name resolution issue.

    The problem certainly could be my ISP, I agree. However, in my experience trying to get them to say anything other than "This is nothing to do with us" is such an enormous hassle that I'd like to try everything I can before I embark on that long, frustrating journey.

    Thank you for the suggestion. smile

    In case anybody's wondering, I'm still getting the "400 Bad Request" page after nearly a day now. Stay tuned for the next exciting installment! tongue

    ps: I love your nickname, strangely_gnarled. smile

  • avatar
    13 sounds
    237 posts


    In Safari try clearing your cached web pages (and/or cookies). Having got the error page once safari may be retrieving the same error page from your hard disc without even attempting to go on-line.

    I love your nickname, strangely_gnarled.
    Thanks. I tried to join freesound with my usual on-line nick "Wibby" but it didn't work and Strangely Gnarled is another pseudonym I've used on my (amateur) website.

    "Spleencast" also raises a smile topped with quizzical eyebrows :?:

    Heaven in the sky is to die for, Heaven on earth is to live for.
  • avatar
    70 sounds
    134 posts


    strangely_gnarled
    In Safari try clearing your cached web pages (and/or cookies). Having got the error page once safari may be retrieving the same error page from your hard disc without even attempting to go on-line.

    That would make sense if I didn't keep getting the same error page when I deliberately refresh it. But when I do, I do, unfortunately.

    strangely_gnarled
    Spleencast
    I love your nickname, strangely_gnarled.
    Thanks. I tried to join freesound with my usual on-line nick "Wibby" but it didn't work and Strangely Gnarled is another pseudonym I've used on my (amateur) website.

    "Spleencast" also raises a smile topped with quizzical eyebrows :?:

    Heh, I usually go by "Lubyanka", but when I signed up here it made sense to me to use the name of my podcast, because my podcast is why I'm here. smile

    (the fact that I hardly ever update it is another story tongue )

    And I call it the spleencast because I think the spleen as a digestive organ and gland is underrated, and also it's a funny name. Two for the price of one! smile

    Still, I'd love to be able to access freesound without having to use a proxy. :/

  • avatar
    13 sounds
    237 posts


    Sorry my suggestions didn't help.

    Hmm.. frustating isn't it!

    Here are my ideas for further enquiry.

    The error message came from a "nginx/0.5.33" server. Perhaps freesound admin could confirm if they use nginx. I suspect not, which means the page request is failing before it even gets to freesound. i.e the problem isn't at the freesound server. (The error page you uploaded cetainly doesn't look like a friendly freesound error page.)

    You could "ping/traceroute"the freesound I.P. address to find out where the trail ends, then look up the domain registration. This will give a clue as to whether the request is actually getting beyond your ISP. ( could ask your ISP if they use nginx/0.5.33?. this version looks pretty old anyway(up to 0.8.29 now), and a web search reveals that later upgrades fixed bugs serving some javascript and/or large files.)

    I don't know anything about the working/configuration of safari & macs I'm afraid, but I still suspect the problem might lie with your ISP.

    Good luck.

    Wibby.

    Heaven in the sky is to die for, Heaven on earth is to live for.

    6 posts