Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#204 Categories with "&" fail with "Bad Request" on URL link!

v1.9
open
nobody
5
2007-04-10
2007-04-10
Tom
No

Categories with "&" fail with "Bad Request" on URL link!

If you create a category with "&" included the resulting category links in the various macro category views will crash with a "Bad Request" whick the link is called.

Discussion

  • Tony Bunce
    Tony Bunce
    2007-06-05

    Logged In: YES
    user_id=408799
    Originator: NO

    Looks like this is a asp.net bug
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;826437

    It is mostly fixed in 2.0 but there are a few exceptions, "*" and ":"
    http://support.microsoft.com/kb/932552

    there are a few solutions:
    -use some custom encoding scheme to re-write category URLs (standard URL rewriting doesn't work)
    -don't allow special characters in category names
    -strip special characters from the category in the url, ("Testing & Deployment" would be the same as "Testing Deployment" though so we dasBlog would have to check for unique names)
    -put the category name after .aspx, URLs are quite as clean, but it gets around the limitation

     
  • Mark McAvoy
    Mark McAvoy
    2007-08-16

    Logged In: YES
    user_id=599314
    Originator: NO

    This issue appears to exist in ASP.NET 2.0. The page renders but the posts dont display as expected when viewing the category containing a '&' character, a similar problem also happens when viewing the RSS feed for the category.

    I have implemented a fix for this problem in the form of a SVN patch, just dont seem to have permission to upload it here.

     
  • Tony Bunce
    Tony Bunce
    2007-08-16

    Logged In: YES
    user_id=408799
    Originator: NO

    I submitted a fix to the dev mailing list a while back that fixed the issue for all special characters in the URL, not just "&"

    It was a somewhat major change so it didn't get committed for the 2.0 release. I'll try and get it committed asap.

    You can post the file by submitting a new patch (took me a while to figure that out):
    https://sourceforge.net/tracker/?group_id=127624&atid=709020