[AOLSERVER] [ aolserver-Bugs-446689 ] nsreturnredirect isn't RFC2068 compliant
Bugs item #446689, was opened at 2001-08-01 00:04 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=103152aid=446689group_id=3152 Category: API: C Group: aolserver4_0 Status: Open Resolution: None Priority: 5 Submitted By: Jerry Asher (jerryasher) Assigned to: Nobody/Anonymous (nobody) Summary: nsreturnredirect isn't RFC2068 compliant Initial Comment: This is broken in aolserver 4, but is also broken in the AOLserver 3.x series. According to RFC 2068, Section 14.30, Location, the Location field must be an absoluteURI. ns_returnredirect doesn't ensure this and will gleefully create and return relative urls. So if a page at /foo/bar does something like: ns_returnredirect index.tcl (presumably intending that the browser should redirect to /foo/bar/nextpage.tcl) What will be returned is: Location: nextpage.tcl It turns out that many browsers such as IE and Netscape understand this and will do the right thing, but other browsers and browser like simulations such as ns_httpget fail to do the right thing and end up returning a 404 (ns_httpget will look for http://host/nextpage.tcl) (I encountered this in both AOLserver/ns_httpget as well as on a web server load tester.) Suggested solutions: 1. Have ns_returnredirect throw an error if the passed in location isn't an absoluteURI (that places the responsibility on the developer to pass in absoluteURIs.) 2. Follow the suggestion of the ACS routine ad_returnredirect and check the location. If it's not an absoluteURI, try and create one using the state of the current connection (using the current directory and the value of the HOST field and/or the driver location.) -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=103152aid=446689group_id=3152
Re: [AOLSERVER] submitting bug report?
On Wed, Aug 01, 2001 at 09:48:38AM +0800, macky wrote: i wanna post a bug report in pertaining to ns_sockopen can some tell how to do that..? http://sourceforge.net/tracker/?atid=103152group_id=3152func=browse It's listed from http://www.aolserver.com/ -Roberto -- +| Roberto Mello - http://www.brasileiro.net |+ Computer Science, Utah State University - http://www.usu.edu USU Free Software GNU/Linux Club - http://fslc.usu.edu Space Dynamics Lab, Developer http://www.sdl.usu.edu No Windows, no cry...
[AOLSERVER] AOL 2.2.3 crashes if outputheaders updated after ns_return
I dunno if this happens with later versions, but thought I'd mention it. This code will crash 2.3.3 every time: ns_return blah ns_set update [ns_conn outputheaders] blah blah I think I remember testing this about 6 mos ago and even a read-reference to outputheaders causes a crash.
[AOLSERVER] [ aolserver-Bugs-446886 ] ns_uuencode only takes 48 chars
Bugs item #446886, was opened at 2001-08-01 11:32 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=103152aid=446886group_id=3152 Category: API: Tcl Group: aolserver3_2 Status: Open Resolution: None Priority: 5 Submitted By: Vinod Kurup (vkurup) Assigned to: Nobody/Anonymous (nobody) Summary: ns_uuencode only takes 48 chars Initial Comment: feature request. ns_uuencode cannot take more than 48 chars which makes it useless in uuencoding binary content. Thanks! -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=103152aid=446886group_id=3152
Re: [AOLSERVER] MIME
On 2001.08.01, Wojciech Kocjan [EMAIL PROTECTED] wrote: I'm currently using mime from tcllib, but it really sucks. It took almost a minute to parse 30kB mail. In my 100% Tcl implementation of an IMAP mail client under AOLserver, I'm using the Tcl MIME package by Marshall Rose, and it works great. Of course, Tcl MIME itself uses Trf by Andreas Kupries to manipulate binary data (probably uses the memchan stuff which rocks) which may explain Tcl MIME's good performance. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/
Re: [AOLSERVER] MIME
Dossy == Dossy [EMAIL PROTECTED] writes: Dossy On 2001.08.01, Wojciech Kocjan [EMAIL PROTECTED] wrote: I'm currently using mime from tcllib, but it really sucks. It took almost a minute to parse 30kB mail. Dossy In my 100% Tcl implementation of an IMAP mail client under Dossy AOLserver, I'm using the Tcl MIME package by Marshall Rose, Dossy and it works great. Of course, Tcl MIME itself uses Trf by Dossy Andreas Kupries to manipulate binary data (probably uses Dossy the memchan stuff which rocks) which may explain Tcl MIME's Dossy good performance. IIRC, you can use Trf instead of the base64 package for encode/decode of binary data in tcllib. In theory the performance should be much better with Trf. -Dan
[AOLSERVER] hello
klasjdlkfjasdl;jfal;sdkjf;lasjdf
Re: [AOLSERVER] MIME
On 1 Aug, Daniel Wickstrom wrote: Dossy == Dossy [EMAIL PROTECTED] writes: Dossy On 2001.08.01, Wojciech Kocjan [EMAIL PROTECTED] wrote: I'm currently using mime from tcllib, but it really sucks. It took almost a minute to parse 30kB mail. Dossy In my 100% Tcl implementation of an IMAP mail client under Dossy AOLserver, I'm using the Tcl MIME package by Marshall Rose, Dossy and it works great. Of course, Tcl MIME itself uses Trf by Dossy Andreas Kupries to manipulate binary data (probably uses Dossy the memchan stuff which rocks) which may explain Tcl MIME's Dossy good performance. IIRC, you can use Trf instead of the base64 package for encode/decode of binary data in tcllib. In theory the performance should be much better with Trf. Yeah, mime 1.2 has some code to handle it, but I tried tclsh+package require Trf first, and it still took about a minute to parse 200kB mail. Any idiot-proof URL to learn on MIME+Trf? I'd like to parse 1MB mail in less than a minute (the destination server is a P3@500MHz for now). Actually, it's what my boss wants (that is - he doesn't want me to kill the server with this software :), I never liked this idea anyway. -- WK
Re: [AOLSERVER] MIME
On 2001.08.01, Wojciech Kocjan [EMAIL PROTECTED] wrote: Yeah, mime 1.2 has some code to handle it, but I tried tclsh+package require Trf first, and it still took about a minute to parse 200kB mail. Any idiot-proof URL to learn on MIME+Trf? I'd like to parse 1MB mail in less than a minute (the destination server is a P3@500MHz for now). Are you talking about using the Tcl MIME package, or mime from tcllib? Tcl MIME is at http://www.oche.de/~akupries/soft/mail/mime.html However, I just tried getting it to display a 1 MB message (consisting of about 4 file attachments around 350 kB each) and AOLserver threw an error in the log/server.log after a while. Oh well. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/
