[Seaside] Issue with moving from Seaside 2.6 to 2.8...
boris at deepcovelabs.com
Thu Jun 12 02:35:52 UTC 2008
Thank you. I'm not sure if my fix is really a fix, but it was the least intrusive override I could find.
-Boris (via BlackBerry)
----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: Seaside - general discussion <seaside at lists.squeakfoundation.org>
Sent: Wed Jun 11 19:33:04 2008
Subject: Re: [Seaside] Issue with moving from Seaside 2.6 to 2.8...
Yup, sorry about the delay. Created AR#54545: "WASessionProtector needs the SeasideRequest to provide #remoteAddress"
for this. Should have an "official" fix shortly.
Boris Popov wrote:
> Oh, yea, I remember now. I raised an issue with Cincom on the list, but
> got no resolution back. The problem as I remember it is that there is no
> way to get at the client IP from the native Opentalk request. Here's the
> override I put in place here to get around the issue,
> SeasideRequest>>doTheWorkFor: aTransport
> | waHandler waRequest wsResponse |
> waRequest := message.
> waRequest headers at: 'x-forwarded-for' put: aTransport id
> [ ... the rest of the method as-is ... ]
> I wouldn't mind a more proper fix from the Opentalk guys though, this is
> a nasty hack.
seaside mailing list
seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside