Assigned
Status Update
Comments
bl...@blainegarrett.com <bl...@blainegarrett.com> #3
Would you be able to provide an example app which produces an error for which gcloud doesn't report, but appcfg.py does?
kn...@google.com <kn...@google.com> #4
In this case it is not app specific, The 400 error is due to quota of the application versions being over the limit which is 10 (but for this specific project it has been increased to 60). So any project with more than 10 versions will experience this.
bl...@blainegarrett.com <bl...@blainegarrett.com> #5
[Comment deleted]
ha...@gmail.com <ha...@gmail.com> #6
Comment has been deleted.
Description
Issue: When python sdk is running on port 9090 and a javascript client is running on a different port (3000), uploading a file via XMLHttpRequest to the /_ah/upload/ handler yields a 405 on the OPTIONS call if any of the cases in the following spec are true:
In my case, I am attempting to track upload progress. When not adding the xhr.upload progress event listener (one of the cases in the above spec) no OPTIONS preflight request is sent and thus no 405. When re-introducing the progress listener, the OPTIONS preflight request is made which 405s and the browser does not yield a response body.
In production, these modules are all the same domain and thus no OPTIONS call is made,
Possible solutions:
- Add a OPTIONS handler (resolves 405)
- Allow devs to set Access headers as part of createUploadUrl()
- or Allow devs to set Access headers for all of _ah/upload