Comments (14)
I'm aware of this, but not sure about 2.2 vs 2.4 usage. From my pov (no backed up numbers), 2.2 is much more commonly seen.
Is adding this breaking note under the repo description a good idea?
from htaccess.
A link to the changes page is probably a good idea. Took me some time to see that they made breaking changes in a minor version step...
from htaccess.
Added it, thanks!
from htaccess.
I didn't see the note about 2.4 in the README until after I forked the repo and added sections for 2.4 and 2.2. Not sure if you would want this added or not but since I wrapped it up I thought I could pass it along:
https://github.com/msumpter/htaccess
2.2 is much more common, but 2.4 is the default Apache install on RHEL/CentOS 7 and Ubuntu 14.04 and eventually these docs will need to be updated to handle both as 2.4 grows in usage.
from htaccess.
Thanks. I totally agree on what you said:
2.2 is much more common, but 2.4 is the default Apache install on RHEL/CentOS 7 and Ubuntu 14.04 and eventually these docs will need to be updated to handle both as 2.4 grows in usage.
But splitting 2.2 and 2.4 config into different sections can make the README look fragmented. Should we make use of comments instead?
## Apache 2.2
Order deny, allow
Deny from all
Allow from xxx.xxx.xxx.xxx
## Apache 2.4
# Require all denied
# Require ip xxx.xxx.xxx.xxx
from htaccess.
But splitting 2.2 and 2.4 config into different sections can make the README look fragmented.
I agree. I feel nobody will need both at the same time, so ideally instead of fragmenting this document its better to have a separate one. This and general instructions on which document to look in for your version makes more sense imho.
from htaccess.
Then this time the repo itself would be cluttered. Also, not every section
is applicable/necessary to be on both documents.
On Tuesday, February 10, 2015, Jude Rosario [email protected]
wrote:
But splitting 2.2 and 2.4 config into different sections can make the
README look fragmented.I feel nobody will need both at the same time, so ideally instead of
fragmenting this document its better to have a separate one. This and
general instructions on which document to look in for your version makes
more sense imho.—
Reply to this email directly or view it on GitHub
#2 (comment).
from htaccess.
Then this time the repo itself would be cluttered. Also, not every section
is applicable/necessary to be on both documents
Agreed, I guess its your call on how to take this project forward. My earlier PR had 2 sections for 2.2 and 2.4 separately
from htaccess.
I think the best solution would be to add two example .htaccess files to the repo, containing all the source commented out.
I.e.:
.htacces.2.2:
## Deny All Access Except Yours
# Order deny, allow
# Deny from all
# Allow from xxx.xxx.xxx.xxx
.htaccess.2.4:
## Deny All Access Except Yours
# Require all denied
# Require ip xxx.xxx.xxx.xxx
The explanation in the README is probably applicable to both of them.
from htaccess.
For the authorization, this snippet can be used to handle both Apache 2.2 and 2.4
<IfModule authz_core_module>
Require all denied
</IfModule>
<IfModule !authz_core_module>
Deny from all
</IfModule>
But I think that if this repo's target public is the github users, and not you (@phanan), you should add snippets to both versions of apache. Since that's your repo, maybe you want to have only snippets that help you (not judging 😄)
from htaccess.
Since that's your repo, maybe you want to have only snippets that help you
Well if this was true, I would just write the "force www" snippet somewhere and stick to it, since it's like the only thing I really ever need...
Now while your snippet may work (I've not tested it), it's kinda redundant I'm afraid. A web master should always know his Apache version thus only needs the respective config.
@a1ee9b Won't this clutter the repo up too? Also, we may end up with redundant info having several files.
I'd love to follow the model of Front-end Job Interview Questions instead -- information is right there when you need it. Guess I'll stick with comments for now. Would be great if @msumpter and @JudeRosario could update the PRs accordingly. Thanks so much!
from htaccess.
Sorry I'm late back into this thread, I agree completely about breaking up the README too much with sub sections. Comments probably are the best way to go for clarity.
from htaccess.
You could have a 2.4 branch and a 2.2 branch, remove the master branch, and make 2.2 the default.
from htaccess.
automatic recognition of #<digits>… sorry!
from htaccess.
Related Issues (20)
- Issue - Redirect git submoudle with kerberos url to HTTP
- Resources Related
- Deny Access to Hidden Files and Directories should handle .well-known
- Order deny,allow HOT 2
- Remove trailing slashes snippet
- cult host liberation HOT 5
- Serve WebP Images works? HOT 1
- Force HTTPS HOT 1
- Remove www with 2nd subdomain for https HOT 1
- Translate to portuguese Brazil HOT 1
- Allow All Access Except Spammers' not working as expected HOT 1
- X-Robots-Tag "noindex, nofollow" HOT 1
- TimeZone HOT 2
- GZIP Compression for CSS Class names? HOT 1
- Claim your Flattr donations HOT 3
- Validate pull requests with Travis
- Force www except for subdomains
- Remove the includeSubDomains from Strict-Transport-Security HOT 4
- How to redirect multiple parameter of query string using htaccess
- Apache 2.2 compatible access control
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from htaccess.