Description
when creating local html documents under the cloned aem content directory, .plain.html requests to these files are not served, resulting in 404s.
To Reproduce
Steps to reproduce the behavior:
- run
aem content clone --all
- create a new file at
content/nav.html and add nav markup to the file to it
- run
aem up
- make a request to nav.plain.html and note that it 404s
Expected behavior
the plain html should be served, as it would be once the content is pushed and previewed
Version:
16.19.8
Description
when creating local html documents under the cloned aem content directory, .plain.html requests to these files are not served, resulting in 404s.
To Reproduce
Steps to reproduce the behavior:
aem content clone --allcontent/nav.htmland add nav markup to the file to itaem upExpected behavior
the plain html should be served, as it would be once the content is pushed and previewed
Version:
16.19.8