Our environment is set up where we have an apache instance with a dispatcher passing the requests back to our Sling instances.
The apache instance prepends either /content/external1 or /content/external2 onto the request before sending it the sling instance(based on domain). In the sling instance we have the sling resource resolver configuration that will remove /content/external1 and /content/external2 from all outgoing paths. This worked fine in our older version of sling(cq5.5) but in our upgraded version(aem6.0) we have a difference with redirects. Previously the redirects would not have the protocol and host name, just the path .. something like "/en_us/software/versions/foo" now the redirect has the full pathing... http://www.sas.com/en_us/software/versions/foo. This is causing a problem as it always specified it as http:// Even when our external request that is hitting apache is in the form of https. Not sure if something changed in Sling or with the new Jetty servlet engine. Any help would be appreciated. -Jason
