Mad Props!

Omniscience is just a Google-search away.
Welcome to Mad Props! Sign in | Join | Help
in Search

The request failed with HTTP status 400: Bad Request

Last post 09-23-2009 12:40 PM by jamesewelch. 5 replies.
Page 1 of 1 (6 items)
Sort Posts: Previous Next
  • 09-22-2009 11:29 AM

    The request failed with HTTP status 400: Bad Request

    I've been uploading comics to the server for the last couple of hours, but now I'm getting an error saying " The request failed with HTTP status 400: Bad Request". I can still query the server (find online) and download and even upload existing comics. I just can't upload new comics.

    It happens consistently on a couple of new comics, but I'm also able to upload new other comics.

    Filed under:
  • 09-22-2009 11:43 AM In reply to

    Re: The request failed with HTTP status 400: Bad Request

    Ok, that's a bit odd.

    Can you quickly knock up a new collection with a single issue that causes this error, and email it through to me (mabster -at- madprops.org)? I will test it here and see if I can diagnose it. Thanks!

    mabster
  • 09-22-2009 11:49 AM In reply to

    Re: The request failed with HTTP status 400: Bad Request

    Ok, I was just able to upload a new issue (Thunderbolts 125) so it must be something specific to the issues you're uploading. I'll wait for your email. :)

    mabster
  • 09-22-2009 12:11 PM In reply to

    Re: The request failed with HTTP status 400: Bad Request

    Email sent with problem issues. It appears to only occur with 3 specific issues. I've uploaded other issues just fine. Its just these 3 issues that are having problems.

  • 09-22-2009 12:22 PM In reply to

    Re: The request failed with HTTP status 400: Bad Request

    Got it. I've uploaded #8 but I'll leave the others so you can test to see if it works.

    Open up the properties of one of the issues, and scroll all the way across to the right in the "Details" text box. There's a unicode character " " at the end of the text that's obviously causing some problems for the web service. Removing that fixes the problem.

    Must be an artifact from the original source of the synopsis text. Not sure if there's a nice way for me to prevent that from happening - we might just have to be aware of it in future.

    mabster
  • 09-23-2009 12:40 PM In reply to

    Re: The request failed with HTTP status 400: Bad Request

     Thanks that fixed it. I didn't notice the extra character at the end.

Page 1 of 1 (6 items)
Powered by Community Server (Non-Commercial Edition), by Telligent Systems