AD0-E117 · Question #24
already points to the load balancer of the AEM environment and final sanity checks are being performed. The website was tested in lower environments without SSL On production, the website is served…
The correct answer is C. Configure Apache Felix Http Service SSL Filter to use the correct SSL forward header. Option C is correct because when SSL is terminated at the load balancer, AEM only sees plain HTTP traffic internally and does not automatically know the original request was HTTPS. Configuring the Apache Felix HTTP Service SSL Filter to recognize the X-Forwarded-Proto header…
Question
already points to the load balancer of the AEM environment and final sanity checks are being performed. The website was tested in lower environments without SSL On production, the website is served over https. During sanity testing, all requests result in a 404. While investigating this issue, an Architect determines the following:
- The requests land on port 443 on the load balancer where SSL is terminated and an HTTP
header X-Forwarded-Proto is set
- The URLs on the website are externalized with http in the absolute links
Which two actions should the Architect take to resolve this problem? (Choose two.)
Options
- BEnsure the Sling Mapping exist at /etc/map/httpj)mwp<.domain.com.443Configure the Adobe
- CConfigure Apache Felix Http Service SSL Filter to use the correct SSL forward header
How the community answered
(22 responses)- B36% (8)
- C64% (14)
Explanation
Option C is correct because when SSL is terminated at the load balancer, AEM only sees plain HTTP traffic internally and does not automatically know the original request was HTTPS. Configuring the Apache Felix HTTP Service SSL Filter to recognize the X-Forwarded-Proto header tells AEM to treat those requests as secure, which ensures it externalizes URLs with https:// rather than http:// - resolving both the mismatched absolute links and the resulting 404s.
Option B is incorrect as written because placing Sling Mappings under /etc/map/http for port 443 is contradictory - port 443 is HTTPS, so the mapping node should live under /etc/map/https. Using the wrong protocol node means AEM's URL mapping never matches the incoming requests, perpetuating 404s rather than fixing them.
Memory tip: Think of the Felix SSL Filter as the "translator" between the load balancer and AEM - without it, AEM is deaf to the X-Forwarded-Proto signal and keeps generating wrong-protocol URLs. For Sling Mappings, the rule is simple: the protocol in the path must match the protocol of the request (/etc/map/https/ for HTTPS, /etc/map/http/ for HTTP).
Topics
Community Discussion
No community discussion yet for this question.