- πΊπΈUnited States ccarnnia
Hi All,
I off load https at the loadballancer and apche vhost is configured for port:80 only.
By default I set /admin/config/content/pathologic to `protocol relative`.
If I mistakenly choose the first option `FULL: URL` then the pages with embeded video or iframes with reative path get mixed mode error.
Should `http` even be an option any more? - πΊπΈUnited States mark_fullmer Tucson
Should `http` even be an option any more?
While, as a web developer, I can't think of a reason in the real world why HTTP would be justified (non-real-world testing, where an SSL certificate is difficult, is an exception), I believe there's an important distinction here:
http
is not an option in Pathologic. TheFull URL
option renders URLs that match the base paths using whatever the site response base URL is. If the response is overhttp
, the links will be rendered withhttp
. If the response ishttps
, all links will be rendered withhttps
.So, while there may be no realistic scenario for
http
, I'm not sure that Pathologic should automatically convert thehttp
protocol tohttps
, regardless of what the site is using.As suggested in comments #7 & #8, an individual site could hook into Pathologic's filter and rewrite the protocol, if desired, using hook_pathologic_alter().
If this were to be done in the module itself, maybe it should take the form of a new configuration option to "Convert HTTP to HTTPS"?