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.

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

401 invalid signature when GET parameters contain unicode characters or SPACE #12

Open
kientux opened this issue Jun 23, 2018 · 3 comments
Assignees

Comments

@kientux
Copy link

kientux commented Jun 23, 2018

If the parameters contain unicode characters (like Vietnamese chars) or space then it will result 401 invalid signature. For example: http://duylv.anhphuongisc.vn/wp-json/wc/v2/products/categories?search=sản phẩm

or even: http://duylv.anhphuongisc.vn/wp-json/wc/v2/products/categories?search=san pham

I tried the same URL in Postman with OAuth 1.0 and it works.

@kientux kientux changed the title 401 invalid signature when GET parameters contain unicode characters 401 invalid signature when GET parameters contain unicode characters or SPACE Jun 23, 2018
@Penait1
Copy link

Penait1 commented Nov 19, 2018

Any solution? The filter[limit] isn't working for me

@omandryk
Copy link
Collaborator

Will try to fix it soon.

@omandryk omandryk self-assigned this Nov 21, 2018
@Penait1
Copy link

Penait1 commented Nov 22, 2018

I found using already url encoded characters makes the signature valid, like so:

filter%5Blimit%5D

But it still only returns 10 results when I use -1 as limit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants