We have a multilingual site following the standard form of /country/language/page, but those pages include an embedded adaptive form. The page content is in the correct language, but the form requires the querystring parameter afAcceptLang in order to load the correct dictionary. This works fine exc...

Thanks, Arun. I suppose it could be related, but that depends on whether or not they consider comments the same as other hidden tags. Sure seems like a bug to me and not a new feature!

I did experiment with doing this, but it didn't seem to work. It really is as if the comment itself ends up as a blank line.

Sorry, but I don't think I can share the full HTML. The image I posted shows the head, and you can clearly see all the blank lines. Each blank line there actually corresponds to a comment in a template.

The comments themselves are not rendered, but a blank line is rendered whenever such a comment is encountered in the code. I have verified this by removing the comments in the templates and reloading the resulting page to see the relevant blank lines removed.I am referring to the extra blank lines t...

We have been trying to eliminate all of the extra blank lines that appear in the markup of our pages, but I have discovered that most of these are actually coming from comments in the template files.For example....Each of those highlighted comments end up as blank lines in the final HTML output. Sin...

Thanks, but this doesn't seem to make any difference. Tried with both http and https nodes and with just the https node. I see the same behavior.

All I see in the request log is the 404 for the root....10.4.0.29 - - [24/Sep/2018:07:58:22 -0700] "GET / HTTP/1.1" 404 198 "-" "Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36"

Well, I have tried many different variations. Let's look at this one for now. I am trying to use the default AMS URL, because our custom dev domain is internal-only DNS.So this is the target that should come up when you hit the root....Claims This is the root, which should map to the above location ...

I am trying to use resource mapping to handle roots for multiple domains in our AEM 6.4 platform, and it's just not working. It seems like they're just ignored.For example....https://domain123.com/content/site123/us/en/ (works)https://domain123.com/ (mapped to path above, throws 404)So the domain is...