Community force.com and standard force.com site throws a 503 when an invalid page name is specified in a site accessed using a custom domain/URL
Last updated 2022-02-10 ·Reference W-2578804 ·Reported By 18 users
Summary
Community force.com and standard force.com site throws a 503 when an invalid page name is specified in a site is accessed using a custom domain/URLs.If you have a custom page for the error it will generate the default 503 force.com versus your custom error page. If using the salesforce community or force.com domain, a 401 unauthorized error is thrown instead.
Repro
An invalid page name is specified in a site accessed using a custom domain/URL.The inconsistency can be reproduced on any active customer site that uses a custom domain.
1. Create a force.com (or community force.com) site.
2. Try to accessing the site using the following URIs (the second should contain at least 1 non-alphanumeric or non-underscore character):
a. http://<domain_prefix>.force.com/page_does_not_exist ==> 404 not found ==> Page Not Found Page
b. http://<domain_prefix>.force.com/page%20does+not%3Dexist ==> 401 unauthorized ==> Authorization Required Page
3. Create a custom domain and custom URL that points to the site.
4. Using the custom domain, access similar URLs:
a. http://<custom_domain>.force.com/page_does_not_exist ==> 404 not found ==> Page Not Found Page
b. http://<custom_domain>.force.com/page%20does+not%3Dexist ==> 503 service unavailable ==> Maintenance Page
Workaround
None
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.