You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The bug is reproducible against the latest release or master.
There are no similar issues or pull requests to fix it yet.
Describe the bug
@aminalaee, I had configured the package with application correctly in http it working file but in production it showing the below error
Mixed Content: The page at '' was loaded over HTTPS, but requested an insecure stylesheet ''. This request has been blocked; the content must be served over HTTPS.
Steps to reproduce the bug
No response
Expected behavior
No response
Actual behavior
No response
Debugging material
No response
Environment
Production
Additional context
No response
The text was updated successfully, but these errors were encountered:
@aminalaee, don't you think the current solution of forwarding the headers is a bit dangerous, since the original request, specially the authentication form, uses http?
I would rather have a way to make sure that all requests leave the browser as https
I'm not sure enforcing the HTTPS is going to be nice for some use-cases. Obviously if you are deploying on a production env you need to take care of that.
Checklist
master
.Describe the bug
@aminalaee, I had configured the package with application correctly in http it working file but in production it showing the below error
Mixed Content: The page at '' was loaded over HTTPS, but requested an insecure stylesheet ''. This request has been blocked; the content must be served over HTTPS.
Steps to reproduce the bug
No response
Expected behavior
No response
Actual behavior
No response
Debugging material
No response
Environment
Production
Additional context
No response
The text was updated successfully, but these errors were encountered: