[ https://issues.apache.org/jira/browse/GUACAMOLE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Jumper reopened GUACAMOLE-437: -------------------------------------- Apparently a UTF-8 non-breaking space was accidentally inserted with these changes: {code:none} 00000000: 2020 2020 7661 7220 6578 7472 6148 6561 var extraHea 00000010: 6465 7273 203d 2065 7874 7261 5475 6e6e ders = extraTunn 00000020: 656c 4865 6164 6572 7320 7c7c c2a0 7b7d elHeaders ||..{} 00000030: 3b0a {code} The space to the left of the two pipe symbols is a normal U+0020 space, however the space to the right is actually U+00A0. This has the side effect of being misinterpreted as "Â" if the JavaScript is read as ISO 8859-1 / CP-1252. > Allow to configure custom headers for Guacamole tunnels > ------------------------------------------------------- > > Key: GUACAMOLE-437 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-437 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-common-js > Reporter: Ignasi Barrera > Priority: Major > Fix For: 1.0.0 > > > When establishing a Guacamole tunnel to an endpoint that requires (for > example) authentication, it is often needed to send custom headers. The > existing withCredentials option works well for session cookies in > cross-domain environments, but when there are no sessions or authentication > relies on headers, there is no way to have an authenticated tunnel request. > A mechanism to configure custom headers for Guacamole tunnels would allow > users to configure custom headers that might be needed for their systems, > such as authentication headers, distributed tracing correlation headers, > request signatures, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)