can this be done on a server with htaccess

[Abby]

Have one htaccess file redirect all 404 pages to a url instead of adding an htacces file to each domain hosted on the server, and what would the htaccess file look like please.

[TheButcher]

I know whatever you do with htaccess you can not get 404 pages on phpbb to go to another url other than the root of the domain, I prefer using individual htaccess files per site because some scripts require certain lines of code.

[Abby]

hello

[HeidiHoe]

Can .htaccess reside above domain level? That's what you'd have to do to control all domains with one file. You might be able to modify your server settings to do this. If you're running CMS, for example wordpress, you would want to make sure you're not creating any conflicts by doing this. Why would you want to do this anyway? It's one lousy line of code in one file per domain. Why give up the flexibility and cause potential issues?

[HeidiHoe]

Not something that I'd recommend but i guess you could just add a meta refresh tag to your 404 page.

Code: Select all

<meta http-equiv="refresh" content="0;URL='https://domain.com/page'" />

The code goes in the head but will work when placed anywhere.

[Abby]

Thanks heidihoe I'll try it now

[gspotman]

My hosting control panel adds a htacess file when I add a new domain to my server.

[HeidiHoe]

My hosting control panel adds a htacess file when I add a new domain to my server.

Within the domain folder, not above it. It controls one particular domain, not all of the domains on the server. Anytime you add domain specific settings in your control panel, such as redirect www for example, a .htaccess file is created containing the directive.

Also, if you manually edit the file removing the code or delete the file altogether, you'll see that the settings in your control panel has changed.

[tacnet]

You can do this in the http.conf file but htaccess files are specific to the domain

Just put this in your htaccess

ErrorDocument 404 https://www.domain.com/404page.html

[gspotman]

My hosting control panel adds a htacess file when I add a new domain to my server.

Within the domain folder, not above it. It controls one particular domain, not all of the domains on the server. Anytime you add domain specific settings in your control panel, such as redirect www for example, a .htaccess file is created containing the directive.

Also, if you manually edit the file removing the code or delete the file altogether, you'll see that the settings in your control panel has changed.

I mean per domain not all sites hosted on the same server

[HeidiHoe]

My hosting control panel adds a htacess file when I add a new domain to my server.

Within the domain folder, not above it. It controls one particular domain, not all of the domains on the server. Anytime you add domain specific settings in your control panel, such as redirect www for example, a .htaccess file is created containing the directive.

Also, if you manually edit the file removing the code or delete the file altogether, you'll see that the settings in your control panel has changed.

I mean per domain not all sites hosted on the same server

Yep. OP wants to set 404 for all domains with one .htaccess file instead of changing server settings. Tacnet replied with the specific file on the server that needs to be modified to accomplish what the OP wants to do. Not a good idea, but whatever

[Hosting Fred]

If you are running the same scripts on the server itwould be okay but if not then do it the usual way , add a .htaccess file per site,my 2 cents.

[XpressPete]

Have one htaccess file redirect all 404 pages to a url instead of adding an htacces file to each domain hosted on the server, and what would the htaccess file look like please.

why would you want to do it that way?

[AlexO]

This has me thinking can you put a wild card htaccess on the server in the public_html level instead?

[HeidiHoe]

This has me thinking can you put a wild card htaccess on the server in the public_html level instead?

.htaccess needs to reside in the domain root of the domain it applies to. When your site loads for a visitor, it will look for .htaccess within the publicly accessible files for the website. That's the domain root folder, not above.

You can store files above that level and link them for download thus preventing direct web access but I don't think you can rig anything similar for .htaccess. Not as far as I know anyways.

If you place .htaccess within a directory folder inside the domain root, it will control anything located within that directory.