This probably wont work for you guys, but the reason why I got that 400 bad request error with tinymce was because in my nginx config I set proxy_set_header as $host:$server_port. This gave a 400 bad request on port 80 but worked fine on port 81. I just figured out that by removing $server_port from the config on the project that ran on port 80 I was able to fix the issue.
On Tuesday, April 22, 2014 4:32:43 PM UTC+10, Heikki Johansson wrote: > > I have the same problem as Eduardo. > > I am using Linode server with setup: > > https -domain > nginx & gunicorn > > django 1.6.2 > mezzanine 3.0.9 > filebrowser-safe - 0.3.3 > grappelli-safe - 0.3.7 > > Whenever I am trying to add image or edit html I get 400 -bad requests. > > With python manage.py runserver I get: > > "GET /asset_proxy/?u= > https://mydomain.com/static/grappelli/tinymce/jscripts/tiny_mce/themes/advanced/source_editor.htm > > HTTP/1.0" 400 > "GET /asset_proxy/?u= > https://mydomain.com/static/grappelli/tinymce/jscripts/tiny_mce/plugins/advimage/image.htm > > HTTP/1.0" 400 > > No idea where these are coming from... > > > torstai, 17. huhtikuuta 2014 10.28.13 UTC+3 Eduardo Sciammarella kirjoitti: >> >> Hi People - >> >> I'm having a difficult time with tinymce. Apologies if this has been >> asked/answered before. I have tried reading all the threads on this issue >> and I am still not able to get it to work. I am a novice so I might be >> missing something that a more advanced person would understand. >> >> I am seemingly having the same issue on localhost and on Heroku. I am >> storing my static files on S3. When I invoke the popup up for tinymce by >> clicking on the 'html' editor from the inline icons - I get a ‘Bad Request >> (400)’ - the response is empty - this is the request url - >> https://127.0.0.1:8000/asset_proxy/?u=https://bucketname.s3.amazonaws.com/static/grappelli/tinymce/jscripts/tiny_mce/themes/advanced/source_editor.htm. >> >> I have this error whether I am running sslserver or runserver. >> >> I am guessing this is most likely a cross-domain issue. I am using >> Mezzanine 3.0.9 - filebrowser-safe==0.3.2 - grappelli-safe==0.3.7 and >> django-s3-folder-storage==0.2 >> >> My settings are: >> DEFAULT_S3_PATH = "media" >> STATIC_S3_PATH = "static" >> S3_URL = 'http://%s.s3.amazonaws.com/' % AWS_STORAGE_BUCKET_NAME >> STATIC_ROOT = "/%s/" % STATIC_S3_PATH >> MEDIA_ROOT = '%s/' % DEFAULT_S3_PATH >> STATIC_URL = '//s3.amazonaws.com/%s/static/' % AWS_STORAGE_BUCKET_NAME >> MEDIA_URL = 'http://s3.amazonaws.com/%s/media/' % AWS_STORAGE_BUCKET_NAME >> ADMIN_MEDIA_PREFIX = STATIC_URL + "grappelli/" >> >> I’m really stumped - any input would be awesome. >> >> Thanks —Edu >> >> >> -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
