The various approach followed for upload service
Created
March 17, 2018 22:07
-
-
Save rambabusaravanan/22a481bf2a8ca6c35e06dcd42c64ef2b to your computer and use it in GitHub Desktop.
Upload Service
POST: https://addons.mozilla.org/en-US/firefox/users/edit
Content-Type: multipart/form-data (csrfmiddlewaretoken, username, email, ..., photo)
Response: HTTP 302 (empty response)
Location: https://addons.mozilla.org/en-US/firefox/users/edit (GET)
Notes: GET is the page request, POST is the api request with 302 of same url (refreshes the page once api is success)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Flock (profle pic)
Notes
On button click, two APIs are sequentially executed. One for media upload, other for other data updates.
Upload Service
POST https://fs.go.to/filesharing/profile_image?token=u6khmkkjmhkunfxxxxxh8l6nfy8fu6mj&guid=rgr966r94wg4rwlg
Content-Type: multipart/form-data (file)
Response Data
Update Profile Service
POST https://proxy.handler.talk.to/go.to/fzeus/v5.0/updateProfile?token=u6khmkkjmhkunfxxxxxh8l6nfy8fu6mj&guid=rgr966r94wg4rwlg
Content-Type: application/json
Request Data
Response Data