-
Notifications
You must be signed in to change notification settings - Fork 660
Baidu: signature authentication support #298
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
Closed
Closed
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
0119015
Baidu: signature authentication support
c2821cb
Add missing spaces for flake8 checking
01f9ae1
Changes for more efficient impl.
0625f35
TestCase for BAIDU AK /w SK
3d5ce65
More accurate exception
da615f0
Add testcase for invalid ak
786db38
Remove EOF blank line
a6b2e97
Minor changes to invalid ak testcase
c6ddce7
Using [geocode|reverse]_run in invalid ak testcase
cab7cfd
Better invalid-ak testcase
d653c16
py2.7 compatible
eb4e5cb
remove compatibility code in testcase
cf9a30e
explicit quote along with urlencode
1009fe2
remove urlencode for compatibility
d10b42c
safe characters SK test
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the docs at http://lbsyun.baidu.com/index.php?title=lbscloud/api/appendix , the
quote(params, safe="/:=&?#+!$,;'@()*[]")code is used for getting a raw string, while there we haveurlencode(params). Wouldn't that cause different hashes for peculiar requests? I think the relevant test cases should be added. For example, a one with a comma:locator.geocode("beijing, china").Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
quoted_paramsinself._url_with_signaturewas given byurlencode.urlencodehas already calledquote_pluson parameters internally. Except parameters,quotenever escape the characters in site/path/key parts, because they are not special characters.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the list of
safecharacters match the one used inurlencodeinternally? For example, I see that comma is in that list, however urlencode uses percent encoding on commas, IIRC.A test wouldn't harm in either way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this patch code doesn't match the given sample code in docs. But it works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It sure works, but for some cases it might not work. Could you please add the test with a comma, and fix the code, if that fails?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's better to stick to docs. I'm going to change
urlencode(params)tourlencode(params, safe="!*'();:@&=+$,/?#[]", quote_via=quote). Will you accept this change?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add the test first :)
But yeah, that would be better than crafting the query string manually. Even better if all of this is not required and a simple
urlencodeworks.