Talk:.htaccess

This article was nominated for deletion on 17 January 2007. The result of the discussion was redirect until it's cleaned up.

Someone please fix the spanish in this article... +sj + 07:23, 22 Apr 2005 (UTC)

Deny users by Country

Is that possible modify the htaccess file to deny by country? --Saphire diablo 10:32, 30 April 2006 (UTC)[reply]

Sure. You can block domains, for instant. You can also deny access to certain IP ranges (you'd have to find them on the web). However, what's the point?

1. It can be easily overridden by an anonymous proxy (lock them if you can).

2. Domains are registered in one country, but administered worldwide. It's possible that some people are in a global TLD, or in another country's (Tuvalu is popular, as is Armenia, or FS of Micronesia).

3. IP ranges are in a complete disarray now. You can't reliably predict the location of the ip address. Even if you can, the reported IP is frequently something completely diferent from the actual IP.

4. Even if you account for all the above, the user will find a way to access your data if it's really that important.

BTW, what data can be so important as to block users from a certain country from accessing it? And what country is it???

I'd assume it'd be for political rather than security purposes... - furrykef (Talk at me) 04:45, 15 August 2006 (UTC)[reply]

Space in url

Can spaces be used in the url for redirection e.g. RedirectPermanent /old%20one.html http://www.wiki.co.nz/new.html this does not seem to work for me, I get a 404 Onco_p53 11:34, 24 July 2006 (UTC)[reply]

404 is a client error. It might be possible that the browser is interpreting the %20 wrong and doesn't change it into a space, but expects actually spelled out "%20" in the address. Have you tried quoting the addresses?

RedirectPermanent "/old%20one.html" "http://www.wiki.co.nz/new.html"

It actually works to quote the old address without the %20 as follows:

Redirect permanent "/old one.html" http://www.wiki.co.nz/new_one.html — Preceding unsigned comment added by 206.138.130.2 (talk) 21:01, 30 July 2011 (UTC)[reply]

HTTP_HOST .htaccess example

The example given for HTTP_HOST does not actually work in .htaccess files, at least with the popular Apache 1.3 server. Does it work with 2.x?

Ok the HTTP_HOST example is fixed.. —The preceding unsigned comment was added by Produke (talk • contribs).

Password protection

AuthGroupFile /dev/null

Is not absolutely necessary, I suggest removing. —The preceding unsigned comment was added by Bah23 (talk • contribs) 12:19, 22 January 2007 (UTC).[reply]

Password protection - htpasswd command

htpasswd /home/newuser/www/stash/.htpasswd newuser

I believe you need -c?? —The preceding unsigned comment was added by Bah23 (talk • contribs) 12:19, 22 January 2007 (UTC).[reply]

Sorry for not signing! I'm new.--Bah23 12:21, 22 January 2007 (UTC)[reply]

I know this is the wrong place to post this... but is there a way to autosign? —The preceding unsigned comment was added by Bah23 (talk • contribs) 12:23, 22 January 2007 (UTC).[reply]

Just type ~~~~ after your message – Qxz 02:13, 23 January 2007 (UTC)[reply]

Article disruption

I think it's disappointing this article has now been stripped of all content, the article was slowly improving and becoming useful, but now it's basically gone! I strongly disagree with this opinion that Wikipedia should focus as an encyclopedia, this makes little sense to me, why not use it for a communal resource, we already have encyclopedias! When I type 'htaccess' in Google, this article is one of the top results, so why can't it tell visitors how to use .htaccess files? Or at least link to resources which can? This article effectively adds to the bulk of rubbish that already exists on the Internet, this site is meant to be an educational resource! Nobody wants an article explaining that a .htaccess file is something you use with the Apache Web Server, whilst this is an important piece of information, visitors needed to be guided to the next stage of learning, either by using this article to explain the file usage, or to link to other content which does! .htaccess files are not part of a commercial product, they are part of an open source project and are supported by millions of web servers, detailed documentation and guidance should un-questionably be included in this article!

CSS example

The CSS example doesn't have much to do with .htaccess, really. He's using a PHP script, and mod_rewrite to redirect the CSS requests to that script. If anything that can be configured via .htaccess belongs in this article, it's going to be a big one...

No filename

If anyone knows why the file has only an extension and no filename, it's probably worth mentioning as it seems a notable point. —Preceding unsigned comment added by 85.211.32.107 (talk) 23:30, 26 December 2007 (UTC)[reply]

Thanks, added explanation to the lead section. It's actually not an extension, just a dot-file. -- intgr [talk] 02:52, 28 December 2007 (UTC)[reply]

Regarding rewrite rules

Although often used in conjunction with PHP. PHP, in fact has nothing to do with the rewrite process itself. I think the explanation of the rewrite module should be reworded. 66.11.77.89 (talk)

What is the purpose of HTAccess File

That means why we are using the Htaccess files —Preceding unsigned comment added by 123.201.129.6 (talk) 05:47, 12 April 2008 (UTC)[reply]

Check out .htaccess#Common usage for why we are using the Htaccess files and for What is the purpose of HTAccess File. Both questions are answered in that one section. Also this here is not the place to talk about the content of the article but rather to discuss the article its self. Perhaps that is your intention. Are you suggesting a rename of "Common usage" section? Im not sure what your asking/telling/typing/trying to say. R00m c (talk) 05:55, 13 April 2008 (UTC)[reply]

creation on windows

it would be good if there was a mention of how you cant make this filename on windows, i.e. it complains you must type a filename —Preceding unsigned comment added by 60.242.227.50 (talk) 07:36, 9 February 2009 (UTC)[reply]

correction needed?

For each HTTP request there are additional file-system accesses for every parent directory when using .htaccess.

Maybe it should read "child directory" instead of "parent directory". Doru001 (talk) 08:26, 29 April 2009 (UTC)[reply]

I guess what was meant is "the directory being accessed and every parent directory thereof"; made sense to me when i first read it. Maybe it's clearer if that statement is rephrased altogether. -- intgr [talk] 17:13, 29 April 2009 (UTC)[reply]

Deletion

Please do not delete this page, I find it very useful. Doru001 (talk) 08:26, 29 April 2009 (UTC) hi how r u ?[reply]