Block a user
b873b1fd0f
Merge pull request 'added CSRF trusted origin config, added tzdata - needed in debug mode' (#22) from sst/some-weird-stuff-with-docker into develop
mhu
deleted branch sst/some-weird-stuff-with-docker from mhu/shimatta-kenkyusho
2024-11-21 00:50:09 +01:00
added CSRF trusted origin config, added tzdata - needed in debug mode
added CSRF trusted origin config, added tzdata - needed in debug mode
As I was finally able to reproduce all that stuff, it's okay.
added CSRF trusted origin config, added tzdata - needed in debug mode
Okay, I think I found the root cause of the issue:
HttpRequest.is_secure(): Returns True if the request is secure; that is, if it was made with HTTPS. Django isn’t magic here: it goes on…
added CSRF trusted origin config, added tzdata - needed in debug mode
https://medium.com/django-deployment/how-to-fix-djangos-https-redirects-in-nginx-63d304ddb19c
Tossing that into the mix as well...
added CSRF trusted origin config, added tzdata - needed in debug mode
I don't get this. This should only be a problem, if django actually wants to check for HTTPS.
added CSRF trusted origin config, added tzdata - needed in debug mode
Warning
Modifying this setting can compromise your site’s security. Ensure you fully understand your setup before changing it.
Make sure ALL of the following are true before setting…
mhu
created branch feature/21-add-package-params in mhu/shimatta-kenkyusho
2024-11-19 21:33:53 +01:00
Add parameters to packages, that can be inherited by components
Port Django to 5.1 with the long term goal to switch to 5.2 which will be LTS supported
correct type conversion in csv import
841be4f1bb
Merge pull request 'correct type conversion in csv import' (#19) from bugfix/import-fuckups into develop
fed63fd45f
Merge pull request 'feature/small-useability-improvements' (#20) from feature/small-useability-improvements into develop
a54cd33880
Merge pull request 'mhu/4-port-to-django-5.1 Port to recent Django version' (#18) from mhu/4-port-to-django-5.1 into develop