Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🔧(backend) fix configuration to avoid different ssl warning #297

Merged
merged 1 commit into from
Oct 1, 2024

Conversation

rouja
Copy link
Contributor

@rouja rouja commented Sep 30, 2024

Fix following warning messages :

  • You have not set a value for the SECURE_HSTS_SECONDS setting.
  • Your SECURE_SSL_REDIRECT setting is not set to True.

Fix following warning messages :
- You have not set a value for the SECURE_HSTS_SECONDS setting.
- Your SECURE_SSL_REDIRECT setting is not set to True.
@AntoLC AntoLC enabled auto-merge (rebase) October 1, 2024 07:19
@AntoLC AntoLC merged commit 3a6bc8c into main Oct 1, 2024
17 checks passed
@AntoLC AntoLC deleted the fix-ssl-warning branch October 1, 2024 07:27
@AntoLC AntoLC mentioned this pull request Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants