Opened 10 years ago
Closed 10 years ago
#1066 closed defect (fixed)
Dianara gets "Invalid Oauth parameter" when passing 'count' or 'offset' params
| Reported by: | JanKusanagi | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 0.8.0 |
| Component: | programming | Keywords: | api, client, feeds, parameters, oauth |
| Cc: | Jessica Tallon | Parent Tickets: |
Description
When trying to fetch a feed from Dianara, like /inbox/major it works great.
However, if Dianara adds parameters to the call, like 'count' to get more activities in one go (the url then being like "/inbox/major?count=30", the server returns "{"error": "Invalid oauth prarameter."}".
I'm unsure if there is something Dianara is not doing right, but this works ok with Pump.io servers.
The OAuth header is generated by QOAuth. I know that, when adding those parameters to the call, those are reflected not only as part of the URL, but as fields in the Authorization header, for some reason.
Maybe that's what's confusing GMG? The fact that there are unexpected values in the Authorization header.
Change History (5)
comment:1 by , 10 years ago
| Milestone: | → 0.8.0 |
|---|
comment:2 by , 10 years ago
| Owner: | set to |
|---|---|
| Status: | new → in_progress |
comment:3 by , 10 years ago
| Owner: | removed |
|---|---|
| Resolution: | → fixed |
| Status: | in_progress → closed |
comment:4 by , 10 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → accepted |
Reopening this one as i'm experiencing this bug in 0.8.0, reverting the fix makes it work as expected.
comment:5 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
This has been fixed as of 3b4ad55, please re-open if you're still experiencing this problem.
Fixed in ce1344f.