When a path that is outside of a domain's custom URLs' path prefixes is accessed on a domain that does not have a root site, error is shown
Trailblazer Community

When a path that is outside of a domain's custom URLs' path prefixes is accessed on a domain that does not have a root site, error is shown

Sites , Communities

Last updated 2021-08-13 ·Reference W-6219031 ·Reported By 42 users

Fixed - Summer '21

Summary
When a request is made on a domain for a path that does not match any of its custom URLs' path prefixes, which means that no custom URL on that domain uses the '/' root path prefix, the error page that is rendered is Salesforce's generic down-for-maintenance page and not a configurable error page.

Repro
To reproduce this issue, access a path that does not exist on a domain that has no '/' root path prefix in its custom URLs. If the first site on the domain, as sorted by the path prefixes in the domain's custom URLs, is a Force.com Site or a Community Force.com Site, Salesforce's generic down-for-maintenance page is displayed instead of that site's 404 error page.

1. Create a new site or community.
2. Set the path prefix of the site to not be the root '/' path prefix, and ensure that no sites use the root '/' path prefix.
3. Access the domain of the site or community with a page that does not exist. Ex. https://example.force.com/page
4. Confirm that you get the Salesforce maintenance page

Workaround
To work around this issue, create a separate Force.com Site with its error pages set to your custom 404 error page. Attach that site to the '/' root path prefix of the domains that require this. Unknown paths on that domain that are outside of that domain's custom URLs' path prefixes will then get served by the root site's custom 404 error page.

1. Go to Setup | App Setup | Develop | Sites. Click on the New button.
2. Fill in the mandatory fields and save the new site. Leave the Default Web Address field empty if the domain that this is needed on is the force.com subdomain.
3. Click on the Page Assignment button in the Error Pages related list.
4. Set all the error pages, except for the Service Not Available page, to your custom Visualforce page for the 404 error and press Save. The Service Not Available field is a static resource and not a Visualforce page.
5. If this workaround is needed on a custom domain, click on the New Custom URL button, set the Domain to the custom domain that this workaround is needed on, ensure that the Path field is set to the / value, and press Save.

Note: This workaround only works for force.com site

As force.com site and community site use different domain, it is not possible to attach a force.com site to the '/' root path prefix of the community domains that require this, so if it is a force.com site, you can create a force.com site in the root path to workaround this and redirect to the 404 error page of the root path force.com site.

If it is a community site, and if you create a community site on the root path of the community domain, currently it is only showing the "URL No Longer Exists" page from the community site in the root path, and you cannot override the 404 error page, so the workaround specified above doesn't apply.

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP10 AP11 AP12 AP13 AP14 AP15 AP16 AP17 AP18 AP19 AP20 AP21 AP22 AP24 AP25 AP26 AP27 AP28 CS1 CS2 CS4 CS5 CS6 CS7 CS8 CS9 CS10 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS100 CS115 CS119 CS110 CS117 CS114 CS113 CS112 CS111 CS11 CS116 CS123 CS122 CS121 CS126 CS127 CS129 CS128 CS125 CS124 CS137 CS138 CS133 CS132 CS14 CS148 CS142 CS159 CS152 CS151 CS15 CS162 CS167 CS166 CS16 CS169 CS165 CS160 CS173 CS17 CS172 CS170 CS171 CS174 CS18 CS189 CS194 CS192 CS193 CS190 CS191 CS199 CS197 CS19 CS198 CS196 CS195 CS20 CS209 CS200 CS202 CS201 CS203 CS21 CS219 CS218 CS217 CS216 CS215 CS214 CS213 CS212 CS211 CS210 CS22 CS220 CS23 CS234 CS24 CS25 CS26 CS27 CS28 CS29 CS31 CS32 CS33 CS34 CS35 CS36 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS47 CS53 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS84 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS94 CS95 CS96 CS97 CS98 CS99 EU16 EU17 EU18 EU19 EU25 EU26 EU27 EU28 EU29 EU30 EU31 EU32 EU33 EU34 EU35 EU36 EU37 EU38 EU39 EU40 EU41 EU42 EU43 EU44 EU45 EU46 EU47 EU48 NA104 NA107 NA109 NA100 NA101 NA103 NA102 NA105 NA119 NA116 NA110 NA118 NA112 NA111 NA115 NA114 NA113 NA117 NA125 NA124 NA122 NA120 NA126 NA127 NA123 NA129 NA121 NA128 NA138 NA134 NA133 NA136 NA135 NA132 NA131 NA130 NA137 NA139 NA140 NA142 NA141 NA149 NA146 NA147 NA148 NA154 NA158 NA159 NA153 NA151 NA155 NA152 NA150 NA156 NA161 NA163 NA167 NA160 NA166 NA165 NA169 NA164 NA168 NA162 NA172 NA170 NA174 NA171 NA173 NA196 NA207 NA204 NA206 NA208 NA209 NA21 NA218 NA214 NA217 NA215 NA212 NA213 NA210 NA65 NA70 NA71 NA75 NA80 NA81 NA82 NA83 NA84 NA85 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 UM1 UM2 UM3 UM4 UM5 UM6 UM7 UM8 UM9

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.