POSTs to wrong path on S3 when editting pre-existing photo in django admin

[evbo]

I am able to create new photos and delete them with the result POSTing an image (uploading it) to my Amazon S3 account.

However, if I go back and edit that photologue photo (say change the name), I get a 400 Invalid Request error from django. It seems that when editing a pre-existing photo, it tries to POST to an admin location (even though the images exist in the media folder - no admin). Again, I can create and delete photos just fine, but editing them causes this error (such as changing tags, name, description, etc).

Here is the log from heroku after I save any changes to a photologue photo:

2014-04-16T23:13:31.889623+00:00 heroku[router]: at=info method=POST path=/admin /photologue/photo/22/ host=myapp.herokuapp.com request_id=blablablabla fwd="x.x.x.x" dyno=web.1 connect=1ms service=997ms sta tus=400 bytes=211

How might photologue be configured so that when editting any changes to a pre-existing photo, it POSTs the result back to the correct location (where it was originally created using the same django admin interface)?

My current work around is every time I need to edit a photo I just delete it and re-upload it with any changes to the meta data I require.