URL parameters are not HTML encoded

Issue #591 resolved
Former user created an issue

Hi Sebastian,

If I click on a user in internet explorer or chrome i see the following error:

"The resource could not be found"

However it is working in Firefox.

I think the problem is that the account names are not being HTML encoded so the backslash that forms part of the fully qualified account name is being interpreted as part of the url.

Firefox seems to be automatically encoding it.

Comments (8)

  1. david smith

    Im running 1.38 SNAPSHOT.

    The problem looks like its with:

    /scm/api/rest/security/permission/user/USERNAME.json

    scm-error.png

    firefox encodes forward slash in the same link as %5C

  2. Log in to comment