This list has become a great resource for JRun developers and sometimes for
Allaire. But Allaire doesn't make money off of mailing lists. This list is
essentially a public newsgroup. Is it hosted by Allaire? No. Does Allaire
anywhere make a statement that this list is an official support forum? No.
Forgive me for being here, but I have as much right to take advantage of it
as anyone. Like most of you, I use the list to my advantage at work. But
JRun and Java happen to be a large part of my interests outside of work as
well. I'm fortunate that way.
As for the cookie thing, it was fixed in build 158 of JRun 2.3.3. Somehow
the fix didn't get into 3.0 SP1. If you really cared, you could have posted
this problem to the official Allaire JRun forum, where people _are_ paid to
answer questions, etc., or called up and reported a bug.
Scott Stirling
Allaire Corporation
http://www.allaire.com/developer/jrunreferencedesk/
> -----Original Message-----
> From: James Brown [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 15, 2000 2:50 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Invalid Cookie Expiration Time
>
>
> Interesting twist Scott. You seem to be a "representative"
> of Allaire and
> seem to be providing support to developers through this
> forum. Does this
> not give the impression that this _is_ an official support forum for
> Allaire? So are you doing this out of the nicety of your
> heart or have you
> been directed to monitor this group and provide support if
> required? If so,
> the numerous times that this has come begs a question about
> the questions
> you pick to answer - or more rightly, not pass along to the
> internal Allaire
> support.
>
> Don't get me wrong. I believe you are providing a good service to the
> people of this forum. It's just that this issue has arisen
> before (and I
> thought I had reported it to Allaire over a year ago) and has
> never been
> touched by yours truly.
>
> Cheers,
> James
>
> > -----Original Message-----
> > From: Scott Stirling [mailto:[EMAIL PROTECTED]]
> > Sent: 2000 September 15 14.57
> > To: '[EMAIL PROTECTED]'
> > Subject: RE: Invalid Cookie Expiration Time
> >
> >
> > Reported where? This list isn't an official support or bug
> tracking forum
> > for Allaire products. If something is serious and falling
> through the
> > cracks, please do like Jeff did and open a support call.
> If it's a bug,
> > there's no charge.
> >
> > Anyway, I believe our support response time was well-within
> the 4 hour
> > limit, although Jeff may not have been in on the call. I
> checked with
> > support. This is a bug, and we are fixing it for JRun 3.0 SP1.
> >
> > Scott Stirling
> > Allaire Corporation
> > http://www.allaire.com/developer/jrunreferencedesk/
> >
> > > -----Original Message-----
> > > From: James Jory [mailto:[EMAIL PROTECTED]]
> > > Sent: Friday, September 15, 2000 1:38 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: RE: Invalid Cookie Expiration Time
> > >
> > >
> > > We reported this several weeks ago and never heard
> anything back from
> > > Allaire. Others have also reported this problem (search
> > > archives on this
> > > list).
> > >
> > > As a work around, we adjust our max age to fall outside of
> > > the 23:59-01:00
> > > range to avoid the bug.
> > >
> > > -James
> > >
> > > -----Original Message-----
> > > Date: Fri, 15 Sep 2000 12:40:46 -0400
> > > From: "Jeff Stevens" <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Subject: RE: Invalid Cookie Expiration Time
> > > Message-ID: <[EMAIL PROTECTED]>
> > >
> > > I think we found the problem to this. One of our developers
> > > decompiled
> > > allaire's code and found the format string they use before
> > > they push the
> > > cookie to the browser is incorrect. Take a look bellow for
> > > details. We
> > > opened a ticket up with Allaire first thing this morning on
> > > this but haven't
> > > heard anything from them. So much for our 4 hr. response
> > > time in the SLA.
> > >
> > > Curious, anyone else having a similar problem? It seems it
> > > only causes
> > > problem on certain browser versions (IE 5.0 for sure). Some
> > > browsers deal
> > > with the 24. Has this been reported before? I'm
> surprised this isn't
> > > causing problems for everyone. We only noticed it because
> > > our sessions
> > > don't work between 2:40 and 3:40 PM when our cookie
> > > expiration time happens
> > > to be at 24:00:00 GMT. Pretty much has been bringing all of
> > > our development
> > > to a halt in the afternoon.
> > >
> > > Unfortunately, we are only using a demo version to decompile
> > > the code so we
> > > can't recompile a fixed version. If anyone is interested in
> > > fixing the code
> > > and recompiling it, we'd definitely be interested in testing
> > > it out come
> > > 2:40 in the afternoon.
> > >
> > > -Jeff
> > >
> > > -----Original Message-----
> > > From: Dave Mimno [mailto:[EMAIL PROTECTED]]
> > > Sent: Friday, September 15, 2000 11:58 AM
> > > To: Luke Hankins; Sean Hogarty; Jeff Stevens
> > > Subject: Cookie problem in JRun
> > >
> > >
> > > Out of curiosity, I decompiled a few JRun classes.
> > >
> > > In the method addVers0() in
> > > allaire.jrun.servlet.JRunCookieUtil, there is
> > > the following code:
> > >
> > > SimpleDateFormat simpledateformat =
> > > new SimpleDateFormat("EEE, dd-MMM-yyyy kk:mm:ss 'GMT'");
> > >
> > > According to the Java 2 APIs, k represents hour in day (1~24). H
> > > represents hour in day (0~23). According to RFC822, date
> > > strings should be
> > > 0~23.
> > >
> > > > -----Original Message-----
> > > > From: Jeff Stevens [mailto:[EMAIL PROTECTED]]
> > > > Sent: Thursday, September 14, 2000 9:19 PM
> > > > To: [EMAIL PROTECTED]
> > > > Subject: Invalid Cookie Expiration Time
> > > >
> > > >
> > > > Ok, I give up here. Why is JRun handing out a cookie that
> > > expires at
> > > > 24:38:33 !?!?! HTTP specs say cookie times should be in
> > > RFC 822 format:
> > > > 0-23. Why is JRun handing out a 24:xx:xx cookie?!?
> > > >
> > > > The reason I ask is that our own cookie (SEID) seems to be
> > > using a 1-24
> > > > format and I think this is causing us some problems.
> > > >
> > > > We are using javax.servlet.http.Cookie and setMaxAge(). Does
> > > > JRun use this
> > > > as well to set it's cookies? Does this point to some bug
> > > in the JRE?
> > > >
> > > > Mmm, what's up?
> > > >
> > > > HTTP/1.1 200 OK
> > > > Server: Microsoft-IIS/5.0
> > > > Date: Fri, 15 Sep 2000 00:38:33 GMT
> > > > Set-Cookie: SEID=2031033;expires=Tue, 28-Aug-2001 05:58:33
> > > GMT;path=/
> > > > Set-Cookie: jsessionid=7121968978313336;expires=Wed,
> > > 15-Sep-1999 24:38:33
> > > > GMT;path=/
> > > > Expires: Thu, 01 Dec 1994 16:00:00 GMT
> > > > Connection: Close
> > > > Cache-Control: no-cache="set-cookie,set-cookie2"
> > > > Content-Type: text/html; charset=ISO-8859-1
> > > >
> > > > ---
> > > > Jeff Stevens
> > > > System Engineer
> > > > Tradeout
> > > > (617) 283-3545
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
