Re: [AOLSERVER] apache compatibility (was: Are the weekly chats officially dead?)
Using a TCL filter and then computing the url with some tcl regexp should do the trick as well. For some "Rewrite module" compatibility, you can write a tcl file that will be read at AS startup, parse the apache file and create the filters. Is that right, or am I missing something ? Regards. Jean-Fabrice RABAUTE Core Services - Enjoy the future today http://www.core-services.fr Mob: +33 (0)6 13 82 67 67 -Message d'origine- De : AOLserver Discussion [mailto:[EMAIL PROTECTED] la part de tammy Envoye : vendredi 1 aout 2003 20:51 A : [EMAIL PROTECTED] Objet : Re: [AOLSERVER] apache compatibility (was: Are the weekly chats officially dead?) This seems really close to what .vuh files do in OpenACS... unless I'm mistaken. Maybe a simple/quick fix is to write a quick script to just parse all the .htaccess rewrite commands into simple .vuh files? Or is there more to this I'm missing? Probably so huh?! t On Friday, August 1, 2003, at 11:01 AM, Patrick Spence wrote: > Peter M. Jansson said: > This is an extract of what is in one of the .htaccess files... Mostly I > think it is just the mod_rewrite and the access control stuff that is > used > for a lot of what is out there.. > > > RewriteEngine On > RewriteBase /gallery/ > RewriteRule ^([^\.\?/]+)/([0-9]+)$ > /gallery/view_photo.php?set_albumName=$1&index=$2 [QSA] > RewriteRule ^([^\.\?/]+)/([A-Za-z_0-9\-]+)$ > /gallery/view_photo.php?set_albumName=$1&id=$2 [QSA] > RewriteRule ^([^\.\?/]+)/$ /gallery/$1 [R] > RewriteRule ^([^\.\?/]+)$ > /gallery/view_album.php?set_albumName=$1 > [QSA] > > -- [EMAIL PROTECTED] -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] apache compatibility (was: Are the weekly chats officially dead?)
This seems really close to what .vuh files do in OpenACS... unless I'm mistaken. Maybe a simple/quick fix is to write a quick script to just parse all the .htaccess rewrite commands into simple .vuh files? Or is there more to this I'm missing? Probably so huh?! t On Friday, August 1, 2003, at 11:01 AM, Patrick Spence wrote: Peter M. Jansson said: This is an extract of what is in one of the .htaccess files... Mostly I think it is just the mod_rewrite and the access control stuff that is used for a lot of what is out there.. RewriteEngine On RewriteBase /gallery/ RewriteRule ^([^\.\?/]+)/([0-9]+)$ /gallery/view_photo.php?set_albumName=$1&index=$2 [QSA] RewriteRule ^([^\.\?/]+)/([A-Za-z_0-9\-]+)$ /gallery/view_photo.php?set_albumName=$1&id=$2 [QSA] RewriteRule ^([^\.\?/]+)/$ /gallery/$1 [R] RewriteRule ^([^\.\?/]+)$ /gallery/view_album.php?set_albumName=$1 [QSA] -- [EMAIL PROTECTED] -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] apache compatibility (was: Are the weekly chats officially dead?)
Peter M. Jansson said: >> the problem isn't >> that the functionality is missing, its not knowning syntax. > > Patrick's case is that he wants to use a 3rd-party package that requires > Apache semantics, and it's not a matter of his knowing the syntax, > (which he probably does anyway), but it's that the 3rd-party packages do > automated things with the .htaccess files and expect them to work. > > What would be helpful would be to collect a list of .htaccess directives > that such packages use, so we could figure out how to support them. This is an extract of what is in one of the .htaccess files... Mostly I think it is just the mod_rewrite and the access control stuff that is used for a lot of what is out there.. RewriteEngine On RewriteBase /gallery/ RewriteRule ^([^\.\?/]+)/([0-9]+)$ /gallery/view_photo.php?set_albumName=$1&index=$2 [QSA] RewriteRule ^([^\.\?/]+)/([A-Za-z_0-9\-]+)$ /gallery/view_photo.php?set_albumName=$1&id=$2 [QSA] RewriteRule ^([^\.\?/]+)/$ /gallery/$1 [R] RewriteRule ^([^\.\?/]+)$ /gallery/view_album.php?set_albumName=$1 [QSA] -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] apache compatibility (was: Are the weekly chats officially dead?)
derek keller said: > apache compatibility in aolserver? band-aid. But if it keeps blood from spurting, a band-aid can indeed be a useful thing. > make some docs for apache users: "how to do apache-specific tasks in > aolserver" with some examples. the problem isn't that the > functionality is missing, its not knowning syntax. No, for me the problem is that there are some wheels that I do not want to spend the months to re-invent.. that should not HAVE to be reinvented... > if someone wants to go as far as to build modules that emulate apache > from within aolserver, there should be a better reason than lack of > time or motivation to learn aolserver on the part of the developer. Such a nice way to be called lazy... Ever hear of the concept of not reinventing the wheel? Why would I write my own html editor, my own gallery software scripts, my own user signup scripts when they already exist and can be leveraged? To replicate the software that I am using would take more than a couple years since I do not have the manpower/resources/money/etc to do so.. when a compatibility layer would be easier to write, help MORE people, and help promote the server software. But I guess I am just a lazy, unmotivated developer.. :) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] apache compatibility (was: Are the weekly chats officially dead?)
> the problem isn't > that the functionality is missing, its not knowning syntax. Patrick's case is that he wants to use a 3rd-party package that requires Apache semantics, and it's not a matter of his knowing the syntax, (which he probably does anyway), but it's that the 3rd-party packages do automated things with the .htaccess files and expect them to work. What would be helpful would be to collect a list of .htaccess directives that such packages use, so we could figure out how to support them. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] apache compatibility (was: Are the weekly chats officially dead?)
apache compatibility in aolserver? band-aid. keep the products separate but functionally similar, which they are. make some docs for apache users: "how to do apache-specific tasks in aolserver" with some examples. the problem isn't that the functionality is missing, its not knowning syntax. if someone wants to go as far as to build modules that emulate apache from within aolserver, there should be a better reason than lack of time or motivation to learn aolserver on the part of the developer. again... to me, as a random lowly aolserver user, this seems to be a matter of comprehensive documentation rather than development needs. --- "Peter M. Jansson" <[EMAIL PROTECTED]> wrote: > > Compatibility with common apache features would go a long way > > towards wider adoption of AS > > Unless it would speed migration away from AOLserver. = "Are you going to spend the rest of your life selling sugar water, or are you going to come with me and change the world?" __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
