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.

Sign up for GitHub

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

Jump to bottom

force https at the boot level instead of in the route files #2110

Merged
merged 1 commit into from
Dec 27, 2023
Merged

force https at the boot level instead of in the route files #2110

merged 1 commit into from
Dec 27, 2023

Conversation

ildyria
Copy link
Member

@ildyria ildyria commented Dec 27, 2023

In theory this should do the job.
Still using force https in reverse proxy is a better solution.

Fixes #2106

@ildyria ildyria added this to the 5.0.1 milestone Dec 27, 2023
@ildyria ildyria requested a review from a team December 27, 2023 09:30
@codecov Codecov
Copy link

codecov bot commented Dec 27, 2023 •
edited

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (ea3dfb4) 85.86% compared to head (97638fc) 85.66%.

Additional details and impacted files

@ildyria ildyria merged commit f518710 into master Dec 27, 2023
33 checks passed
@ildyria ildyria deleted the add-force-https-to-boot branch December 27, 2023 09:57
@ildyria ildyria mentioned this pull request Dec 31, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@qwerty287 qwerty287 qwerty287 approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
5.0.1
Development

Successfully merging this pull request may close these issues.

css and js assets not loaded after upgrade to v5 using docker
2 participants
@ildyria @qwerty287