Re: [AOLSERVER] apache compatibility
derek keller said: > granted, i am probably missing the picture of what you need. if you > have an existing set of permissions and url rewrites on your apache > installation in a big bunch of scattered htaccess files, it wouldn't be > hard to translate those into aolserver's url registeration and > permissions stuff. make a tcl script that translates your htaccess > files to tcl configs. then post that script and the method you used so > that someone else could do the same thing into a "how to migrate url > rewrites and permissions from apache to aolserver without the headache" > doc. The rewrite stuff is only half of the problems I am dealing with.. I need to put AS4.0 on a system and try out it's virtual hosting to see if it eliminates the other problems I was having with the virtual hosting package I was using... > that way, you can solve the same problem as apache in the > aolserver-approved way without having to duplicate apache code in a > runtime environment. > > again, i may be missing something... and none of this helps you to do > it in the meantime anyway. it is a cascading effect of wanting/needing to use certain tools that make it easier to do things a certain way.. but make it a LOT easier to do 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
i didn't mean any personal criticism. what i do mean is that it's not easy to move between systems, especially when you don't have the time or money to spend doing it. in these situations, if docs existed it might make the transition easier as there probably are elements of apache functionality that already do exist in aolserver. granted, i am probably missing the picture of what you need. if you have an existing set of permissions and url rewrites on your apache installation in a big bunch of scattered htaccess files, it wouldn't be hard to translate those into aolserver's url registeration and permissions stuff. make a tcl script that translates your htaccess files to tcl configs. then post that script and the method you used so that someone else could do the same thing into a "how to migrate url rewrites and permissions from apache to aolserver without the headache" doc. that way, you can solve the same problem as apache in the aolserver-approved way without having to duplicate apache code in a runtime environment. again, i may be missing something... and none of this helps you to do it in the meantime anyway. > 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] > __ 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.
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] Are the weekly chats officially dead?
Peter M. Jansson said: >> Compatibility with common apache features would go a long way >> towards wider adoption of AS > > Unless it would speed migration away from AOLserver. I don't see how it would speed the migration.. in fact it would have kept me from moving my stuff away...by adding functionality, especially as an add on module, it increases the likelyhood that someone will not migrate away to -get- that functionality... I love aolserver, I think it is a very stable (for me), fast, powerful server.. I love the tcl being built in.. I love how stuff works with it... but it isn't a "fit" any more... I have grown in my needs to other directions... I still help maintain it at work, most of our work servers run it.. but for some things it doesn't work out.. which is depressing to be honest. -- 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] IM'ed URLs not being logged
+-- On Aug 1, Daniel P. Stasinski said: | In the tcpdump thats I posted in the last hour, the first hit | returned the image (and response 200) but it was never logged . | The second hit was when I clicked the refresh button and it | returned 304 and WAS logged. It works the same way with text | files. Sounds like you need to put AOLserver under the debugger and step through a request. -- 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, are docs the answer?
I really like this idea. Compiling a how to do this apache thing using AOLserver tools would go a long way. AOLserver users would see what cool things Apache can do, and we can learn areas where AOLserver can't do what Apache can do. From there we would need to decide if we want AOLserver to do those things at all. I really doubt an apache compatability layer would be extremely complex due to the complete different way of handling requests, Dave On Fri, Aug 01, 2003 at 10:02:43AM -0700, derek keller wrote: > 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. > -- Dave Bauer [EMAIL PROTECTED] http://www.thedesignexperience.org -- 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.
Re: [AOLSERVER] Are the weekly chats officially dead?
On Fri, Aug 01, 2003 at 12:08:38PM +0200, Zoran Vasiljevic wrote: > > Funny that your putting this out :) > > Some years (1, 2?) ago, I was tinkering with the idea of how > to bring DAV (faster) to AS and one of the considerations > was to snap-in Apache-layer and use mod_dav as-is. Musea Technologies has been working on a port of mod_dav to AOLserver. > The fact that Apache is now also going MT would mean > that many mod_x modules will have to be made MT-safe > which could simplify the work. > I'm afraid that we'd need to make some internal changes > in AS C-API, but it would be worth the effort. It would be a good selling point, no doubt. -Roberto -- +|Roberto Mello -http://www.brasileiro.net/ |--+ + Computer Science Graduate Student, Utah State University + + USU Free Software & GNU/Linux Club - http://fslc.usu.edu/ + "Please return stewardess to original upright position" -- 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] IM'ed URLs not being logged
> I don't see anything weird about the HTTP request. Try > creating a dummy file, like /foo.txt, containing just a > few ASCII characters, and see if you can reproduce the > problem with that URL. If so, post a tcpdump of that. In the tcpdump thats I posted in the last hour, the first hit returned the image (and response 200) but it was never logged . The second hit was when I clicked the refresh button and it returned 304 and WAS logged. It works the same way with text files. This is the only log entry: 66.62.93.30 - - [01/Aug/2003:08:51:08 -0700] "GET /desertdawn.jpg HTTP/1.1" 304 0 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Q312461)" Also, no log entry of you downloading the tcpdump file (just the incorrect url you tried) 24.153.164.125 - - [01/Aug/2003:09:19:53 -0700] "GET /tcpdump.ou HTTP/1.0" 404 531 "" "Wget/1.8.2" url: http://www.avenues.org/desertdawn.jpg tcpdump: http://www.avenues.org/tcpdump.out nsd.tcl: http://www.avenues.org/nsd.tcl (snippet of nslog section) Daniel P. Stasinski Software Engineer Mayor Pharmaceutical Laboratories [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] IM'ed URLs not being logged
I don't see anything weird about the HTTP request. Try creating a dummy file, like /foo.txt, containing just a few ASCII characters, and see if you can reproduce the problem with that URL. If so, post a tcpdump of that. -- 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] Are the weekly chats officially dead?
> Compatibility with common apache features would go a long way > towards wider adoption of AS Unless it would speed migration away from AOLserver. -- 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] IM'ed URLs not being logged
> Is this file supposed to be 269 bytes? It looks like it > just contains a HTTP request. Where's the tcpdump data > itself? Sorry, try again. Daniel P. Stasinski Software Engineer Mayor Pharmaceutical Laboratories [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] forcing headers on aolserver 3.4.2
On Fri, Aug 01, 2003 at 11:05:27AM -0400, Jason Cook wrote: > [01/Aug/2003:10:37:47][1169.1][-main-] Error: > no current connection > while executing > "ns_conn outputheaders" > invoked from within > "ns_set put [ns_conn outputheaders] "AUTHOR" "Internet Services" > " > (file > "/servers/test/modules/tcl/test.tcl" line 1) > > host# cat test.tcl > ns_set put [ns_conn outputheaders] "AUTHOR" "Internet Services" You've put your "test.tcl" file in the wrong place. Above, it looks like it's in a tcl library directory, which means it is getting sourced at AOLserver startup time by thread "main", which is NOT a connection thread, thus the "no current connection" error. You need to put test.tcl in your www/ directory instead, then hit "http://mysite.com/test.tc.l"; to test it. -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.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.
Re: [AOLSERVER] forcing headers on aolserver 3.4.2
On Fri, 1 Aug 2003, Jason Cook wrote: > I'm having a problem trying to force a header on aolserver 3.4.2. > > I found some docs on http://webmaster.info.aol.com/aolserver.html, but > when I try even that specific example, it returns the following error: > > [01/Aug/2003:10:37:47][1169.1][-main-] Error: > no current connection > while executing > "ns_conn outputheaders" > invoked from within > "ns_set put [ns_conn outputheaders] "AUTHOR" "Internet Services" > " > (file > "/servers/test/modules/tcl/test.tcl" line 1) > > host# cat test.tcl > ns_set put [ns_conn outputheaders] "AUTHOR" "Internet Services" > host# > > Can anyone let me know what I may be doing wrong? > > Thanks for your help. > n/m .. tcl module programming 101, I fixed it :) thanks! -j -- 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] Are the weekly chats officially dead?
not that I remember - but most of it (if not all of it is Tcl based so it'd fairly easy to add that) > -Original Message- > From: AOLserver Discussion [mailto:[EMAIL PROTECTED] Behalf > Of Patrick Spence > Sent: Friday, August 01, 2003 4:04 PM > To: [EMAIL PROTECTED] > Subject: Re: [AOLSERVER] Are the weekly chats officially dead? > > > Does it work using instructions in a .htaccess file? > > - Original Message - > From: "Tim Moss" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, August 01, 2003 1:14 AM > Subject: Re: [AOLSERVER] Are the weekly chats officially dead? > > > > > > > > > 2: full emulation of mod_rewrite and .htaccess files > > > > > > I know this isn't what you want to hear, but ... if you want Apache, > > > then run Apache. :-) > > > > > > > And the nsrewrite module worked last time I tried! > > > > > > Tim Moss > > SiteSpeed Ltd > > Email: [EMAIL PROTECTED] > > Website:http://www.site-speed.co.uk > > > > This email contains information from SiteSpeed Ltd, which may be > privileged > > or confidential. If you are not the intended recipient, be > aware that any > > disclosure, copying, distribution or use of the contents of this > information > > is prohibited. If you have received this electronic message in error, > please > > notify us immediately. > > > > > > -- > > 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. > -- 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] forcing headers on aolserver 3.4.2
I'm having a problem trying to force a header on aolserver 3.4.2. I found some docs on http://webmaster.info.aol.com/aolserver.html, but when I try even that specific example, it returns the following error: [01/Aug/2003:10:37:47][1169.1][-main-] Error: no current connection while executing "ns_conn outputheaders" invoked from within "ns_set put [ns_conn outputheaders] "AUTHOR" "Internet Services" " (file "/servers/test/modules/tcl/test.tcl" line 1) host# cat test.tcl ns_set put [ns_conn outputheaders] "AUTHOR" "Internet Services" host# Can anyone let me know what I may be doing wrong? Thanks for your help. -j -- 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] Are the weekly chats officially dead?
I am familiar with the concept, I use one Daniel Stasinski wrote.. though when I used AS for my personal site I used the functionality of AS to do the same... but for this particular use (the gallery software), and for similar functionality in other third party software I really need something that is compatible with how Apache does it...rather than having to manually go in and create the URLs each time something changes, or write a filter that processes it all first using Regexp (not my strong suit of programming to say the least)... Compatibility with common apache features would go a long way towards wider adoption of AS - Original Message - From: "Mat Kovach" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 01, 2003 7:39 AM Subject: Re: [AOLSERVER] Are the weekly chats officially dead? > On Thu, Jul 31, 2003 at 10:18:01PM -0700, Patrick Spence wrote: > } the main one I am concerned with is a script for subscriptions that > } handles via .htaccess entries.. the next most used set is the rewrite > } stuff done by Gallery (gallery.menalto.com) which is primarily just > } rewrite commands to make friendly URLs out of url encoded ones.. > > I have a tinyurl.com clone written using AOLserver and Postgres > (shouldn't be very hard to port to use about any DB) which does > make "nice" urls (http://myturl.com/software/dist/). I'm working > it into OpenACS ( to provide nice 'Email This Link' for pages). > > The basic functionlity is fairly generic and should be easy to move > into other projects. > > Mat Kovach > > > -- > 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] Are the weekly chats officially dead?
Does it work using instructions in a .htaccess file? - Original Message - From: "Tim Moss" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 01, 2003 1:14 AM Subject: Re: [AOLSERVER] Are the weekly chats officially dead? > > > > > 2: full emulation of mod_rewrite and .htaccess files > > > > I know this isn't what you want to hear, but ... if you want Apache, > > then run Apache. :-) > > > > And the nsrewrite module worked last time I tried! > > > Tim Moss > SiteSpeed Ltd > Email: [EMAIL PROTECTED] > Website:http://www.site-speed.co.uk > > This email contains information from SiteSpeed Ltd, which may be privileged > or confidential. If you are not the intended recipient, be aware that any > disclosure, copying, distribution or use of the contents of this information > is prohibited. If you have received this electronic message in error, please > notify us immediately. > > > -- > 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] IM'ed URLs not being logged
On 2003.08.01, Daniel P. Stasinski <[EMAIL PROTECTED]> wrote: > > Capture the entire HTTP request that isn't logged, > > using "tcpdump -s 2000 -w tcpdump.out port 80" or > > similar. Give us a URL to download tcpdump.out > > so we can examine it. > > http://www.avenues.org/tcpdump.out Is this file supposed to be 269 bytes? It looks like it just contains a HTTP request. Where's the tcpdump data itself? -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- 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] Are the weekly chats officially dead?
> I have a tinyurl.com clone written using AOLserver and > Postgres (shouldn't be very hard to port to use about > any DB) which does make "nice" urls Spiffy, I did the same at http://oneweek.org a while back. Never advertised it though, just gave it friends and people here on the list. Daniel P. Stasinski Software Engineer Mayor Pharmaceutical Laboratories [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] Are the weekly chats officially dead?
On Thu, Jul 31, 2003 at 10:18:01PM -0700, Patrick Spence wrote: } the main one I am concerned with is a script for subscriptions that } handles via .htaccess entries.. the next most used set is the rewrite } stuff done by Gallery (gallery.menalto.com) which is primarily just } rewrite commands to make friendly URLs out of url encoded ones.. I have a tinyurl.com clone written using AOLserver and Postgres (shouldn't be very hard to port to use about any DB) which does make "nice" urls (http://myturl.com/software/dist/). I'm working it into OpenACS ( to provide nice 'Email This Link' for pages). The basic functionlity is fairly generic and should be easy to move into other projects. Mat Kovach -- 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] Are the weekly chats officially dead?
Yes, I am able and willing to do this. I was also taking over as moderator for the core team meetings starting next week, but it appears you and/or Mark now have the time to devote to that role and you have a set of agenda items so I'll step back from that role. /s. On Friday, August 1, 2003, at 09:36 AM, Nathan Folkman wrote: we need an owners for the webdav module and the rest of the modules as well. scott, are you still able and willing to coordinate this effort? it would be nice to have one point person for each module who would coordinate feature requests, track bugs, review code, ect. Dossy wrote: Yes, yes yes! I was thinking of using tDOM as well, that's awesome. That, and David Walker (grax) has also done some work on the nsdav code as well. Perhaps at some point I'll merge everything together, and we'll have something decent. Hey, someone else also announced a WebDAV module on the AOLserver mailing list -- I wonder how far they got with theirs ... -- Nathan Folkman Technical Mgr., AOLserver/NPE/NES Web Services and Publishing -- 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] IM'ed URLs not being logged
> Capture the entire HTTP request that isn't logged, > using "tcpdump -s 2000 -w tcpdump.out port 80" or > similar. Give us a URL to download tcpdump.out > so we can examine it. http://www.avenues.org/tcpdump.out I typed in a url directly into IE and simply pressed ENTER. Nothing in the access log and I had not previously viewed this image. When doing a forced refresh, the entry appeared. I've had other users who there is no way possible they had viewed an image prior to the moment, when the go to a URL it does not appear in the access log. I am in AIM as DanielStasinski if you want to do a live test. Daniel P. Stasinski Software Engineer Mayor Pharmaceutical Laboratories [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] Are the weekly chats officially dead?
we need an owners for the webdav module and the rest of the modules as well. scott, are you still able and willing to coordinate this effort? it would be nice to have one point person for each module who would coordinate feature requests, track bugs, review code, ect. Dossy wrote: > > Yes, yes yes! I was thinking of using tDOM as well, that's awesome. > That, and David Walker (grax) has also done some work on the nsdav code > as well. Perhaps at some point I'll merge everything together, and > we'll have something decent. > > Hey, someone else also announced a WebDAV module on the AOLserver > mailing list -- I wonder how far they got with theirs ... -- Nathan Folkman Technical Mgr., AOLserver/NPE/NES Web Services and Publishing -- 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] Are the weekly chats officially dead?
In a message dated 8/1/2003 1:55:22 AM Eastern Daylight Time, [EMAIL PROTECTED] writes: Roberto Mello wrote:> - Readline support for nscp.That would be quite hard, since readline also has to guess the terminaltype and so on.Wouldn't it be much better to write nscp client in Tcl+readline or evenTk. I have a pretty generic ztelnet module, which I use to connect.It's pretty old and nasty, but proved that writing a quite simplesocket/ssl connecting tool is pretty easy. Then adding command history... and things would start working pretty well.Tk could also allow editing multiline commands - using [info complete].I often do nested foreach loops so checking completeness helps me a lot. Yes -- direct readline would be too hard. In fact, it was in there once long ago and was very messy and hard to maintain. A separate app, perhaps a Tk thingy, which communicates with nscp makes a lot of sense. -Jim -- 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] Are the weekly chats officially dead?
On 2003.08.01, Nathan Folkman <[EMAIL PROTECTED]> wrote: > > In a message dated 8/1/03 6:08:13 AM, [EMAIL PROTECTED] writes: > > > I was tinkering with the idea of how > > to bring DAV (faster) to AS > > > which reminds me... ;-) jay and i took dossy's orginal nsdav code and > modified it to use tdom for xml creation and parsing. we'll be > releasing it as soon as we find a few minutes to check the code in. it > doesn't have everything, locking for example, but is very simple and > fast. Yes, yes yes! I was thinking of using tDOM as well, that's awesome. That, and David Walker (grax) has also done some work on the nsdav code as well. Perhaps at some point I'll merge everything together, and we'll have something decent. Hey, someone else also announced a WebDAV module on the AOLserver mailing list -- I wonder how far they got with theirs ... -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- 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] Are the weekly chats officially dead?
On Friday 01 August 2003 13:19, you wrote: > In a message dated 8/1/03 6:08:13 AM, [EMAIL PROTECTED] writes: > > I was tinkering with the idea of how > > to bring DAV (faster) to AS > > which reminds me... ;-) jay and i took dossy's orginal nsdav code and > modified it to use tdom for xml creation and parsing. we'll be releasing it > as soon as we find a few minutes to check the code in. it doesn't have > everything, locking for example, but is very simple and fast. Heh, this news is good news :) Many roads lead to Rome! Zoran -- 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] Are the weekly chats officially dead?
In a message dated 8/1/03 6:08:13 AM, [EMAIL PROTECTED] writes: I was tinkering with the idea of how to bring DAV (faster) to AS which reminds me... ;-) jay and i took dossy's orginal nsdav code and modified it to use tdom for xml creation and parsing. we'll be releasing it as soon as we find a few minutes to check the code in. it doesn't have everything, locking for example, but is very simple and fast. -- 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] Are the weekly chats officially dead?
On Friday 01 August 2003 07:19, you wrote: > Nathan Folkman said: > > perhaps its time to look at what it would take to provide a simple apache > > compatibility layer that would allow apache modules to be used > > (unmodified) > > within aolserver. i've not had time to fully investigate, so this could > > be the > > wrong approach, and maybe wouldn't even be possible or feasible. > Funny that your putting this out :) Some years (1, 2?) ago, I was tinkering with the idea of how to bring DAV (faster) to AS and one of the considerations was to snap-in Apache-layer and use mod_dav as-is. The fact that Apache is now also going MT would mean that many mod_x modules will have to be made MT-safe which could simplify the work. I'm afraid that we'd need to make some internal changes in AS C-API, but it would be worth the effort. Cheers Zoran -- 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] Are the weekly chats officially dead?
> > > 2: full emulation of mod_rewrite and .htaccess files > > I know this isn't what you want to hear, but ... if you want Apache, > then run Apache. :-) > And the nsrewrite module worked last time I tried! Tim Moss SiteSpeed Ltd Email: [EMAIL PROTECTED] Website:http://www.site-speed.co.uk This email contains information from SiteSpeed Ltd, which may be privileged or confidential. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us immediately. -- 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.
