You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Michael Jumper (JIRA)" <ji...@apache.org> on 2016/08/14 01:06:20 UTC

[jira] [Resolved] (GUACAMOLE-74) Share keys containing slashes cause REST API to fail

     [ https://issues.apache.org/jira/browse/GUACAMOLE-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Jumper resolved GUACAMOLE-74.
-------------------------------------
    Resolution: Fixed

> Share keys containing slashes cause REST API to fail
> ----------------------------------------------------
>
>                 Key: GUACAMOLE-74
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-74
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>            Priority: Blocker
>             Fix For: 0.9.10-incubating
>
>
> It's hard to tell if it's Tomcat or Jersey or a limitation of the Java servlet API, but both "%2F" and "/" within the path universally end up interpreted as "/", causing trouble if a path component actually needs to contain a slash and, thus, contains "%2F".
> As Guacamole's share keys frequently contain slashes, and the identifier of a connection provided due to a share key is simply the share key itself, attempts to retrieve connection information like the name, protocol, etc. fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)