Deployment - htaccess for shared hosting servers

[lluz]

📚 Docs or angular.io bug report

Description

An addition to the "Deployment" documentation.

🔬 Minimal Reproduction

What's the affected URL?

https://angular.io/guide/deployment

Reproduction Steps

Go to the "Fallback configuration examples"

Expected vs Actual Behavior

Addition to the 'Apache section':

RewriteEngine on
RewriteCond %{REQUEST_FILENAME} -s [OR]
RewriteCond %{REQUEST_FILENAME} -l [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^.*$ - [NC,L]
RewriteRule ^(.*) index.html [NC,L]

I followed this comment:
#11884 (comment)

📷Screenshot

🔥 Exception or Error

🌍 Your Environment

Browser info

Anything else relevant?

Distribution uploaded to a regular shared Apache server.

[jenniferfell]

Notes to writer:
https://angular.io/guide/deployment#fallback-configuration-examples

The .htaccess shown above should be used instead of what's in the doc.

[jenniferfell]

@lluz : Thank you for researching this and letting us know. My team isn't currently set up to test Apache. Is there any chance you'd be willing to submit a PR for the doc update, based on what worked for you? See Contributing to Angular for more info.

[lluz]

@jenniferfell
Thanks for picking up on this minor issue.
Unfortunately I am no expert on Apache so I am unable to describe (comment) the solution and compare/check if it is better than the one currently documented.
The only thing I know is that it is a complementary option that works well on my common Apache shared hosting servers.
I have however called out to @gthomas2 ( #11884 (comment) ) to see if he would be willing to make the pull request.
Hope someone with the right skills can pick this up, because it is a bit annoying when you publish a distribution (Javascript web app) to a common basic Apache server only to find out that a simple browser page refresh (F5) will give you a "Not Found" default server page.

[rockument69]

Looks like we need engineering input for this.

[josephperrott]

Closing this out as a duplicate of #21201

As noted in the closing comment of #21201 (comment), while the proposed configuration is valid and will work. We are not providing a production ready configuration to be used, the intention is for this to be a basic configuration for a simple development environment as a starting point. The current configuration we use has good compatibility and is easy to reason about what the lines of the configuration do.

Currently security practice recommendation for production apache use as I understand it is actually to use a httpd.conf file rather than .htaccess file anyway.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}