Tickets :: Comment on [#8200] Aviary's Phoenix image editor support

* Your Email Address
* Spam protection	Enter the letters below: . .. ..__ .__ . . \|\ \|\|\ \|[__)[__)\|\ \| \| \\|\| \\|[__)\| \| \\|
Comment	> Looking at this further, I think we should probably wait until this > API matures a bit, or the "advanced api" version is implemented. With > the simple API there is no shared secret between the client server > and Aviary, only a client specified identifier for each image that is > passed to Aviary in a GET request. After saving the image, Aviary > POSTS back to the client server a URL to find the new image, along > with the same identifier that was originally passed in the clear via > GET. So, unless I'm missing something, it would theoretically be > possible for a 3rd party to hijack this identifier and cause the > user's image to be replaced.
Attachment
Watch this ticket