{"id":444,"date":"2012-05-23T10:08:14","date_gmt":"2012-05-23T10:08:14","guid":{"rendered":"http:\/\/www.extradrm.com\/?p=444"},"modified":"2012-05-23T10:08:14","modified_gmt":"2012-05-23T10:08:14","slug":"personnaliser-les-pages-erreurs-via-htaccess","status":"publish","type":"post","link":"https:\/\/www.extradrm.com\/?p=444","title":{"rendered":"Personnaliser les pages erreurs via .htaccess"},"content":{"rendered":"

one<\/strong> of<\/strong><\/strong> the<\/strong><\/strong> most<\/strong> dis<\/strong>cussed<\/strong> topics<\/strong> here<\/strong> is<\/strong> the<\/strong><\/strong> importance<\/strong> of<\/strong><\/strong> a 404<\/strong><\/strong> page<\/strong> returning<\/strong> a “real<\/strong>” 404<\/strong><\/strong> header<\/strong>. Amazingly, the<\/strong><\/strong>re are thousands of<\/strong><\/strong> “custom 404<\/strong><\/strong> error tutorials” on the<\/strong><\/strong> web that don’t touch this<\/strong> is<\/strong>sue. If you set up a custom 404<\/strong><\/strong> using .htaccess, the<\/strong><\/strong> server will still return a status of<\/strong><\/strong> 200 OK, because the<\/strong><\/strong> original status is<\/strong> lost in the<\/strong><\/strong> redirect. This<\/strong> is<\/strong> a “big deal.” <\/span><\/p>\n

For the<\/strong><\/strong> unaware, let’s take the<\/strong><\/strong> worst case: you set up a 404<\/strong><\/strong> to redirect to the<\/strong><\/strong> home page<\/strong>. page<\/strong> not found, put the<\/strong><\/strong>m back on main page<\/strong>. Bad idea, if the<\/strong><\/strong> search engines capture a few bad links, the<\/strong><\/strong>y are going to index your 404<\/strong><\/strong> page<\/strong> – which is<\/strong> duplicate content for your main page<\/strong>, which gives you duplicate content penalties. For your main page<\/strong>. OUCH. <\/span><\/p>\n

Secondly, many have had trouble creating the<\/strong><\/strong>ir Google site verification page<\/strong> because the<\/strong><\/strong>y use a custom 404<\/strong><\/strong> page<\/strong>, as Google won’t verify a site that returns a 200 for a non-exis<\/strong>tent page<\/strong>. <\/span><\/p>\n

So I’ve spent a few hours this<\/strong> AM looking around. Unfortunately, I was only able to locate two veins of<\/strong><\/strong> comments on how to get a custom error page<\/strong> to return a 404<\/strong><\/strong> header<\/strong>.<\/strong> This<\/strong> first was helpful comments supplying no real<\/strong> resolution: <\/span><\/p>\n\n\n\n
\n\n\n\n
a URL that does not exis<\/strong>t should be returning<\/strong> a 404<\/strong><\/strong> [Not Found] <\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n


\n<\/span><\/p>\n\n\n\n
\n\n\n\n
Some domains have improperly configured the<\/strong><\/strong>ir custom error page<\/strong> . . . <\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n


\n<\/span><\/p>\n\n\n\n
\n\n\n\n

\nYou need to make sure your custom error page<\/strong> returns a proper 404<\/strong><\/strong> header<\/strong>. If you’re returning<\/strong> a 200 OK, Sitemaps won’t verify your site. <\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

OKAY, we get it, the<\/strong><\/strong> custom error “page<\/strong>” needs to generate a 404<\/strong><\/strong> header<\/strong>. So how do we do that? the<\/strong><\/strong> reason for quoting “page<\/strong>” became apparent when I encountered this<\/strong>: <\/span><\/p>\n\n\n\n
\n\n\n\n
DO NOT use static html page<\/strong>s for this<\/strong> — you can’t change the<\/strong><\/strong> result code on a static html page<\/strong>. <\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Now we’re getting down to it – when we think of<\/strong><\/strong> “page<\/strong>s” most<\/strong> of<\/strong><\/strong> us think of<\/strong><\/strong> static html.<\/em> An .asp page<\/strong>, php page<\/strong>, or a perl scripts are real<\/strong>ly dynamic page<\/strong> output and not static page<\/strong>s. Yet almost<\/strong> every resource on the<\/strong><\/strong> web on custom error page<\/strong>s instructs to create a static page<\/strong> to a custom error page<\/strong>. <\/span><\/p>\n

<debate>
\nthe<\/strong><\/strong> second bit of<\/strong><\/strong> mis<\/strong>information I encountered that using a forward -slash path in your directive will preserve the<\/strong><\/strong> 404<\/strong><\/strong> status: <\/span><\/p>\n

ErrorDocument 404<\/strong><\/strong> \/my_error.html <\/span><\/p>\n

This<\/strong> is<\/strong> also (apparently?) false, I have tested it thoroughly, an error document at root still returns 200 header<\/strong>s when the<\/strong><\/strong> page<\/strong> is<\/strong> dis<\/strong>played because it loses the<\/strong><\/strong> original 404<\/strong><\/strong> in the<\/strong><\/strong> redirect.
\n<\/debate> <\/span><\/p>\n

the<\/strong><\/strong> second vein of<\/strong><\/strong> comments has to do with solving this<\/strong> is<\/strong>sue but what I still consider workarounds:<\/strong> <\/span><\/p>\n\n\n\n
\n\n\n\n
Temporarily dis<\/strong>able custom 404<\/strong><\/strong> error page<\/strong>s for your site\/Check if your web server return correct 404<\/strong><\/strong> code for non exis<\/strong>ting page<\/strong>s\/verify file\/Restore your 404<\/strong><\/strong> custom error page<\/strong>s. <\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

This<\/strong> will work for getting past the<\/strong><\/strong> Google verification, but you still have a permanent is<\/strong>sue with non exis<\/strong>tent page<\/strong>s generating a 200 OK. <\/span><\/p>\n

Because static HTML won’t generate http header<\/strong>s, a scripting method<\/em> is<\/strong> the<\/strong><\/strong> suggested usage in most<\/strong> cases. <\/span><\/p>\n

PHP:
\n<\/span><\/p>\n\n\n\n
\n\n\n\n

\n<?php
\nheader<\/strong>(“HTTP\/1.0 404<\/strong><\/strong> Not Found”);
\n?>
\n<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

ASP:
\n<\/span><\/p>\n\n\n\n
\n\n\n\n

\n<%
\nResponse.Status = “404<\/strong><\/strong> Not Found”
\n%>
\n<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Perl:
\n<\/span><\/p>\n\n\n\n
\n\n\n\n

\nprint “Status: HTTP\/1.1 404<\/strong><\/strong> Not Foundn”;
\nprint “Content-type: text\/htmlnn”;
\n<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

So here<\/strong> is<\/strong> the<\/strong><\/strong> question:<\/strong> I still consider the<\/strong><\/strong>se workarounds. I have my perl scripts printing the<\/strong><\/strong> 404<\/strong><\/strong> status where<\/strong> appropriate, but it seems like the<\/strong><\/strong>se shouldn’t be necessary. is<\/strong> the<\/strong><\/strong>re a CORRECT way to simply use the<\/strong><\/strong> 404<\/strong><\/strong> directive to our advantage without relying on an external tool to return the<\/strong><\/strong> appropriate header<\/strong>? <\/span><\/p>\n

 <\/p>\n

 <\/p>\n

Il existe pas mal de templates pr\u00e9-existants pour avoir une mise en page bien plus belle que celle g\u00e9n\u00e9r\u00e9e par Apache.<\/p>\n

Tout d\u2019abord, ajoutez ceci dans votre fichier .htacess \u00e0 la racine ou le r\u00e9pertoire concern\u00e9.<\/p>\n

ErrorDocument 301 \/erreurs\/301-moved_permanently.php
\nErrorDocument 302 \/erreurs\/302-moved_temporarily.php
\nErrorDocument 303 \/erreurs\/303-see_other.php
\nErrorDocument 400 \/erreurs\/400-bad_request.php
\nErrorDocument 401 \/erreurs\/401-authorization_required.php
\nErrorDocument 402 \/erreurs\/402-payment_required.php
\nErrorDocument 403 \/erreurs\/403-forbidden.php
\nErrorDocument 404 \/erreurs\/404-not_found.php
\nErrorDocument 405 \/erreurs\/405-method_not_allowed.php
\nErrorDocument 406 \/erreurs\/406-not_acceptable.php
\nErrorDocument 407 \/erreurs\/407-proxy_authentication_required.php
\nErrorDocument 408 \/erreurs\/408-request_timed_out.php
\nErrorDocument 409 \/erreurs\/409-conflicting_request.php
\nErrorDocument 410 \/erreurs\/410-gone.php
\nErrorDocument 411 \/erreurs\/411-content_length_required.php
\nErrorDocument 412 \/erreurs\/412-precondition_failed.php
\nErrorDocument 413 \/erreurs\/413-request_entity_too_long.php
\nErrorDocument 414 \/erreurs\/414-request_uri_too_long.php
\nErrorDocument 415 \/erreurs\/415-unsupported_media_type.php
\nErrorDocument 500 \/erreurs\/500-internal_server_error.php
\nErrorDocument 501 \/erreurs\/501-not_implemented.php
\nErrorDocument 502 \/erreurs\/502-bad_gateway.php
\nErrorDocument 503 \/erreurs\/503-service_unavailable.php
\nErrorDocument 504 \/erreurs\/504-gateway_timeout.php
\nErrorDocument 505 \/erreurs\/505-http_version_not_supported.php<\/p>\n","protected":false},"excerpt":{"rendered":"

one of the most discussed topics here is the importance of a 404 page returning a “real” 404 header. Amazingly, there are thousands of “custom 404 error tutorials” on the web that don’t touch...<\/p>\n","protected":false},"author":1,"featured_media":2849,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[29],"tags":[],"youtube_video":null,"_links":{"self":[{"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/posts\/444"}],"collection":[{"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=444"}],"version-history":[{"count":0,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/posts\/444\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/media\/2849"}],"wp:attachment":[{"href":"https:\/\/www.extradrm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=444"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=444"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=444"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}