homepage Welcome to WebmasterWorld Guest from 54.243.13.30
register, free tools, login, search, subscribe, help, library, announcements, recent posts, open posts,
Subscribe and Support WebmasterWorld
Home / Forums Index / Code, Content, and Presentation / Apache Web Server
Forum Library, Charter, Moderators: Ocean10000 & incrediBILL & phranque

Apache Web Server Forum

    
.htaccess validator?
keyplyr




msg:1516145
 8:06 am on Sep 5, 2002 (gmt 0)

Is there a way to check for mistakes in .htaccess ?

 

Filipe




msg:1516146
 9:52 pm on Sep 6, 2002 (gmt 0)

I hate to see a post left unanswered, so here's my response:

I've never seen a .htaccess validator, nor have I been able to find one in my searches for an answer to post. It's very odd that there isn't one though, dontcha think?

jeremy goodrich




msg:1516147
 9:54 pm on Sep 6, 2002 (gmt 0)

Best advice I could give you is pour over the apache.org info, and read / reread until it finally starts to make sense.

Between that and beta testing on a live web server, seems to work well enough (though I don't know any cool tricks).

keyplyr




msg:1516148
 11:49 pm on Sep 6, 2002 (gmt 0)

> It's very odd that there isn't one though, dontcha think?

Yeah. There seems to be software that checks syntax for everything else. How else could I compare it to standards? The 'various browser checking' method seems to be the least efficient.

> Best advice I could give you is pour over the apache.org info, and read / reread until it finally starts to make sense.

Thanks, I do all that (kinda) but even when/if I understand how to accomplish a task using .htaccess, I'm always uncertain about spacing, certain character use and sequence or other more effective alternatives.

andreasfriedrich




msg:1516149
 12:04 am on Sep 7, 2002 (gmt 0)

Yeah. There seems to be software that checks syntax for everything else. How else could I compare it to standards? The 'various browser checking' method seems to be the least efficient.

Do not mix up syntax and content. All a .htaccess validator could do was to check the syntax. Whether that syntactically correct configuration does what you want it to do would still have to be checked using what you refer to as the 'various browser checking' method.

I don´t really see the need for a validator since interoperability is not an issue here. It´s about making a valid Apache configuration file that cannot be used for any other webserver. So how do you validate it then? Just copy it into the desired directory and request a page in that directory. If there is a syntax error you´ll get a 500 error.

Of course you shouldn´t be doing this on your live server. But I would suspect anybody who would want to do some serious webdevelopement would have a test server.

For HTML and a lot of other web standards it is a totally different situation. The standard to validate your code against is the DTD/spec and not some browser´s implementation of it.

keyplyr




msg:1516150
 6:01 am on Sep 7, 2002 (gmt 0)


Thanks for those comments andreasfriedrich. I don't know about maintaining a test server, but I get your point.

Global Options:
 top home search open messages active posts  
 

Home / Forums Index / Code, Content, and Presentation / Apache Web Server
rss feed

All trademarks and copyrights held by respective owners. Member comments are owned by the poster.
Terms of Service ¦ Privacy Policy ¦ Report Problem ¦ About
© Webmaster World 1996-2014 all rights reserved