ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Disallowed Key Characters.... not a cookie issue

May 21, 2010 1:36pm

Subscribe [3]
  • #1 / May 21, 2010 1:36pm

    Chris Newton

    440 posts

    So one of my domains has the following problem:

    A url like this does not work:
    http://domain.com/ee/?/store/downloads/FSW1NTmV5ejhmQVIwNTQ=

    But this does:
    http://domain.com/ee/?/store/downloads/FSW1NTmV5ejhmQVIwNTQ=

    Is the % character disallowed in URLs? I wouldn’t think so… it’s a pretty standard URL encoding character. Any ideas?

  • #2 / May 21, 2010 4:22pm

    Sue Crocker

    26054 posts

    Chris, not seeing the % in either link. ....

    Which version/build of ExpressionEngine 1.6.x are you using? You can find that out at the bottom of any control panel page.

    The current version of the 1.6.x branch is 1.6.9 and the build is 20100430.

    When you say it doesn’t work, what do you mean?

  • #3 / May 21, 2010 5:30pm

    Chris Newton

    440 posts

    Sorry, the EE boards converted the “% 3 d” character to =

    the following is the failing link (remove the spaces)

    fails
    <a href="http://domain.com/ee/?/store/downloads/FSW1NTmV5ejhmQVIwNTQ">http://domain.com/ee/?/store/downloads/FSW1NTmV5ejhmQVIwNTQ</a> % 3 d 
    
    does not fail.
    <a href="http://domain.com/ee/?/store/downloads/FSW1NTmV5ejhmQVIwNTQ=">http://domain.com/ee/?/store/downloads/FSW1NTmV5ejhmQVIwNTQ=</a>
  • #4 / May 21, 2010 5:33pm

    Chris Newton

    440 posts

    EE vs. 1.6.8, build 20091201

  • #5 / May 21, 2010 5:34pm

    Chris Newton

    440 posts

    And, sorry, in the subject i mentioned the crux of the problem, but not in the post.

    If I go to the “failed” link, I get the following output on the page:

    Disallowed Key Characters

    And it’s not due to a cookie issue… EE’s choking on the encoded = sign in the URL.

  • #6 / May 21, 2010 7:33pm

    Brandon Jones

    5500 posts

    I think it’s more likely the ? in the URL that’s causing the problem. EE sees it and expects a valid key (as in key/value pair). But first, we’ll need to troubleshoot without any sort of URL rewriting and with index.php back in the URLs.

  • #7 / May 21, 2010 7:50pm

    Chris Newton

    440 posts

    We made a workaround, so as far as I’m concerned, you can close this out. For us… the point is now moot.

    Thanks for the help 😊

  • #8 / May 21, 2010 8:27pm

    Brandon Jones

    5500 posts

    Ah, no problem. Glad you’re up and running.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases