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

Query panel in workbench doesn't work with non latin characters using POST #454

Closed
abrokenjester opened this issue Sep 7, 2016 · 2 comments
Closed

Query panel in workbench doesn't work with non latin characters using POST #454

abrokenjester opened this issue Sep 7, 2016 · 2 comments
Labels
🐞 bug issue is a bug duplicate issue is a duplicate (close reason) 📦 workbench affects the RDF4J Workbench

Comments

@abrokenjester
Copy link
Contributor

(Migrated from https://openrdf.atlassian.net/browse/SES-1811)

I have found out that the query panel seems to have problems with non latin characters when the query is send by POST.

I have attached two query examples:

The first one is send using GET and works fine

The second one is send using POST and gives the following error: " Lexical error at line 9, column 37. Encountered: "\u00a5" (165), after : ""

This is using a UTF-8 based Tomcat connector. If I change to an ISO-based connector, I have the same problem in both cases.
@abrokenjester abrokenjester added the 🐞 bug issue is a bug label Sep 7, 2016
@catch-point catch-point added the 📦 workbench affects the RDF4J Workbench label Jun 23, 2017
@barthanssens
Copy link
Contributor

Related to / duplicate of #391 ?

@abrokenjester abrokenjester added the duplicate issue is a duplicate (close reason) label Aug 13, 2018
@abrokenjester
Copy link
Contributor Author

yeah, looks like a duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🐞 bug issue is a bug duplicate issue is a duplicate (close reason) 📦 workbench affects the RDF4J Workbench
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@abrokenjester @catch-point @barthanssens