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

Russion query returns 400 BAD REQUEST #38

Open
klokan opened this issue Oct 6, 2016 · 1 comment
Open

Russion query returns 400 BAD REQUEST #38

klokan opened this issue Oct 6, 2016 · 1 comment
Assignees
@MartinMikita
Labels
bug
Milestone
v2.1

Comments

@klokan
Copy link
Member

klokan commented Oct 6, 2016 •
edited
Loading

Sample query: ялча

http://search.osmnames.org/q/%D1%8F%D0%BB%D1%87%D0%B0.js

Reported by @Komzpa at https://twitter.com/komzpa/status/783722445228351488

The CORS is not a problem (I see the Access-Control-Allow-Origin: * header).

The problem is probably status code 400 BAD REQUEST - returned by Flask for some reason.

It may be also related to required improvement of Unicode charset indexing, where we need to improve Sphinx search config. See #20
@klokan klokan added the bug label Oct 6, 2016
@klokan
Copy link
Member Author

klokan commented Jul 13, 2017 •
edited
Loading

It can be solved by applying unidecode on the index #20 as well as the query.

@MartinMikita MartinMikita modified the milestone: v2.0 Jul 13, 2017
@klokan klokan modified the milestones: v2.0, v2.1 Aug 31, 2017
@philippks philippks mentioned this issue Sep 22, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MartinMikita MartinMikita

Labels
bug
Projects
None yet
Milestone
v2.1
Development

No branches or pull requests
2 participants
@klokan @MartinMikita