Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Using non-ascii signs in user names will cause a crash in shinyproxy and thus in clinsight #125

Closed
LDSamson opened this issue Nov 4, 2024 · 0 comments
Closed

Using non-ascii signs in user names will cause a crash in shinyproxy and thus in clinsight #125

LDSamson opened this issue Nov 4, 2024 · 0 comments
Assignees
@LDSamson
Labels
bug Something isn't working

Comments

@LDSamson
Copy link
Collaborator

LDSamson commented Nov 4, 2024

See issue reported here.

Root cause is that apparently only ascii signs can be transferred in HTTP headers, and a workaround is to always use base64 encoding to transfer user names.
@LDSamson LDSamson self-assigned this Nov 4, 2024
@LDSamson LDSamson added the bug Something isn't working label Nov 4, 2024
@LDSamson LDSamson mentioned this issue Nov 4, 2024
Merged
@LDSamson LDSamson changed the title Using non-ascii signs in user names will cause a cras in shinyproxy and thus in clinsight Using non-ascii signs in user names will cause a crash in shinyproxy and thus in clinsight Nov 5, 2024
@LDSamson LDSamson closed this as completed Nov 5, 2024
@LDSamson LDSamson mentioned this issue Nov 15, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LDSamson LDSamson

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@LDSamson