[COUCHDB-1035] oauth handler always expect json encoded value for key, start_key ...

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 1.1, 1.2
• Component/s: HTTP Interface
• Skill Level: New Contributors Level (Easy)
• Assignee: Unassigned
• Reporter: Benoit Chesneau
• Created: 20/Jan/11 12:52
• Updated: 02/Sep/18 06:31
• Resolved: 02/Sep/18 06:31

Description

oauth handler always expect json encoded value for key, start_key ... even the path isn't a view, list or all_docs resources:

Path: "/testdb/_design/legacyapp/_show/post/essai?id=essai&key=test"

[debug] [<0.121.0>] OAuth Params: [

{"id","essai"}

,

{"key","test"}

]
[error] [<0.121.0>] attempted upload of invalid JSON (set log_level to debug to log it)
[debug] [<0.121.0>] Invalid JSON: <<"test">>

If you are OK i will provide a patch that only try to encode when it's needed.

Issue Links

• is duplicated by: COUCHDB-1439 `key`, `startkey`, `endkey` query parameters seems to have valid json value for show/update handlers.