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
{{ message }}
This repository has been archived by the owner on Jun 19, 2024. It is now read-only.
setting site_url (which will be the complete URI of the site root) doesn't need to be defined without the www, when adding the www-redirect in the system settings. Actually, it must not, and here's why:
Consider a site that has a FormIt Ajax-Call to a responder-template that responds JSON. This will have the site_url domain.com and be receiving a request from www.domain.com and therefore violate the CORS policy unless you explicitly allow cross-origin requests (which will be too high-level for most users).
Correct config would consequently be site_url WITH the www - so the final version of it and http_host WITHOUT it to make it redirectable.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
setting site_url (which will be the complete URI of the site root) doesn't need to be defined without the www, when adding the www-redirect in the system settings. Actually, it must not, and here's why:
Consider a site that has a FormIt Ajax-Call to a responder-template that responds JSON. This will have the site_url domain.com and be receiving a request from www.domain.com and therefore violate the CORS policy unless you explicitly allow cross-origin requests (which will be too high-level for most users).
Correct config would consequently be site_url WITH the www - so the final version of it and http_host WITHOUT it to make it redirectable.
The text was updated successfully, but these errors were encountered: