Opened 9 years ago
Closed 9 years ago
#1048 closed defect (fixed)
Pumpa image upload failed
| Reported by: | Jessica Tallon | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 0.8.0 |
| Component: | programming | Keywords: | api, federation |
| Cc: | Parent Tickets: |
Description
An error occurs whilst trying to upload an image from pumpa. You should be able to upload the image.
Change History (5)
comment:1 by , 9 years ago
| Milestone: | → 0.8.0 |
|---|
comment:3 by , 9 years ago
The problem for Pumpa is not the object itself. The object is wrapped in an activity:
{
object: { ... }
verb: post
}
And Pumpa expects every object and activity it receives to have a unique id (or url) so that it can keep track of them. This activity doesn't have any of those.
comment:5 by , 9 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This should now work, the activity has a valid, globally unique ID as well as all other attributes except "to", "cc", "bcc", "bto" which are currently not supported in GNU MediaGoblin.
The nonce max length no longer is an issue as discussed above.
Note:
See TracTickets
for help on using tickets.
The problem seemed to be that MediaGoblin had a minimum nonce length of 20 and a maximum of 30 characters. Pumpa is sending shorter nonces. I have lowered the maximum nonce length to 5, i wasn't able to find a minimum nonce length in OAuth library Evan uses.
This change was made: 8d8fdfd.
Pumpa is segfaulting when i receives the JSON response from the image upload, a copy of the JSON can be found at: http://pamrel.lu/353ed/