Smalltalk › Frameworks & Tools › Seaside › Seaside General

Re: Issue with moving from Seaside 2.6 to 2.8...

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 7 messages Options
Boris Popov, DeepCove Labs (SNN)
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Issue with moving from Seaside 2.6 to 2.8...

Boris Popov, DeepCove Labs (SNN)

Never mind, sorry, didn't scroll far enough. That looks like the problem that was fixed a while ago, I would load the latest from public repository and check again.

Cheers!

-Boris (via BlackBerry)

From: [hidden email]
To: [hidden email]
Sent: Wed Jun 11 07:12:29 2008
Subject: Re: [Seaside] Issue with moving from Seaside 2.6 to 2.8...

Who is calling it? A bit of stack print would help. I suspect its a session protector? It was probably fixed after release, did you load from public repository or parcels?

Cheers!

-Boris (via BlackBerry)

From: [hidden email]
To: Seaside - general discussion
Sent: Wed Jun 11 07:09:43 2008
Subject: [Seaside] Issue with moving from Seaside 2.6 to 2.8...

Hi all.. 

I'm back to work some more Seaside code after having been away from it for almost a year.  
Anyway, I've got a new VW 7.6 image loaded up with the latest Seaside/Glorp + others and
then I loaded my app and tried running it and get the following stack dump when the code 
is looking for #remoteAddress on a Seaside.WARequest object..  Any ideas on what's messed
up?  I did notice that the config page of Seaside is vastly different when configuring each app
and I'm impressed with how that works now -- even my Glorp stuff is showing up there -- very
slick!  Anyway, if you've got any ideas on this issue below, that would be great!  MTIA!

-- Rick

Message not understood: #remoteAddress

Debug Proceed

Possible Causes

  • you sent a message this type of object doesn't understand

Stack Trace

  1. thisContext
    Seaside.SeasideRequest(Object)>>doesNotUnderstand:
    self
    SeasideRequest[GET /seaside/myscrip HTTP/1.1 Host: localhost:7777 User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_5_2; en-us) AppleWebKit/525.13 (KHTML, like Gecko) Version/3.1 Safari/525.13 Referer: http://localhost:7777/seaside Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-language: en-us Accept-encoding: gzip,deflate Connection: keep-alive ]{GET /seaside/myscrip headers: Dictionary ('accept-language'->'en-us' 'connection'->'keep-alive' 'accept-encoding'->'gzip, deflate' 'user-agent'->'Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_5_2; en-us) AppleWebKit/525....etc...
    aMessage
    a Message with selector: #remoteAddress and arguments: #()
    excpt
    a MessageNotUnderstood
    resumeValue
    nil
  2. thisContext
    optimized [] in Seaside.WASessionProtector>>remoteAddressFromRequest:
    self
    BlockClosure [] in Seaside.WASessionProtector>>remoteAddressFromRequest:
    aRequest
    a Seaside.WARequest GET /seaside/myscrip
  3. thisContext
    Dictionary>>at:ifAbsent:
    self
    Dictionary ('accept-language'->'en-us' 'connection'->'keep-alive' 'accept-encoding'->'gzip, deflate'...etc...
    key
    'x-forwarded-for'
    aBlock
    BlockClosure [] in Seaside.WASessionProtector>>remoteAddressFromRequest:
    index
    2
    obj
    nil
  4. thisContext
    Seaside.WARequest>>headerAt:ifAbsent:
    self
    a Seaside.WARequest GET /seaside/myscrip
    aKey
    'x-forwarded-for'
    aBlock
    BlockClosure [] in Seaside.WASessionProtector>>remoteAddressFromRequest:
  5. thisContext
    Seaside.WASessionProtector>>remoteAddressFromRequest:
    self
    a Seaside.WASessionProtector
    aRequest
    a Seaside.WARequest GET /seaside/myscrip
  6. thisContext
    Seaside.WASessionProtector>>verifyRequest:
    self
    a Seaside.WASessionProtector
    aRequest
    a Seaside.WARequest GET /seaside/myscrip
  7. thisContext
    Seaside.WASessionProtector>>updateRoot:
    self
    a Seaside.WASessionProtector
    html
    a Seaside.WAHtmlRoot
  8. thisContext
    optimized [] in Seaside.WASessionContinuation>>updateRoot:
    self
    BlockClosure [] in Seaside.WASessionContinuation>>updateRoot:
    each
    a Seaside.WASessionProtector
    aHtmlRoot
    a Seaside.WAHtmlRoot
  9. thisContext
    Seaside.WASessionProtector(Seaside.WAPresenter)>>withNextPresentersDo:
    self
    a Seaside.WASessionProtector
    aBlock
    BlockClosure [] in Seaside.WASessionContinuation>>updateRoot:
  10. thisContext
    optimized [] in Seaside.WAPresenter>>withNextPresentersDo:
    self
    BlockClosure [] in Seaside.WAPresenter>>withNextPresentersDo:
    ea
    a Seaside.WASessionProtector
    aBlock
    BlockClosure [] in Seaside.WASessionContinuation>>updateRoot:
  11. thisContext
    MyScrip.MSWApplicationMain(Seaside.WAComponent)>>decorationChainDo:
    self
    a MyScrip.MSWApplicationMain
    aBlock
    BlockClosure [] in Seaside.WAPresenter>>withNextPresentersDo:
  12. thisContext
    optimized [] in Seaside.WAComponent>>nextPresentersDo:
    self
    BlockClosure [] in Seaside.WAComponent>>nextPresentersDo:
    ea
    a MyScrip.MSWApplicationMain
    aBlock
    BlockClosure [] in Seaside.WAPresenter>>withNextPresentersDo:
  13. thisContext
    optimized [] in [] in Seaside.WAComponent>>childrenDo:
    self
    BlockClosure [] in [] in Seaside.WAComponent>>childrenDo:
    aBlock
    BlockClosure [] in Seaside.WAComponent>>nextPresentersDo:
    ea
    a MyScrip.MSWApplicationMain
  14. thisContext
    BlockClosure>>cull:
    self
    BlockClosure [] in [] in Seaside.WAComponent>>childrenDo:
    anObject
    a MyScrip.MSWApplicationMain
  15. thisContext
    MyScrip.MSWApplicationMain(Object)>>ifNotNil:
    self
    a MyScrip.MSWApplicationMain
    aBlock
    BlockClosure [] in [] in Seaside.WAComponent>>childrenDo:
  16. thisContext
    optimized [] in Seaside.WAComponent>>childrenDo:
    self
    BlockClosure [] in Seaside.WAComponent>>childrenDo:
    ea
    a MyScrip.MSWApplicationMain
    aBlock
    BlockClosure [] in Seaside.WAComponent>>nextPresentersDo:
  17. thisContext
    Array(SequenceableCollection)>>do:
    self
    #(a MyScrip.MSWApplicationMain)
    aBlock
    BlockClosure [] in Seaside.WAComponent>>childrenDo:
    i
    1
  18. thisContext
    Seaside.WAToolFrame(Seaside.WAComponent)>>childrenDo:
    self
    a Seaside.WAToolFrame
    aBlock
    BlockClosure [] in Seaside.WAComponent>>nextPresentersDo:
  19. thisContext
    Seaside.WAToolFrame(Seaside.WAComponent)>>nextPresentersDo:
    self
    a Seaside.WAToolFrame
    aBlock
    BlockClosure [] in Seaside.WAPresenter>>withNextPresentersDo:
  20. thisContext
    Seaside.WAToolFrame(Seaside.WAPresenter)>>withNextPresentersDo:
    self
    a Seaside.WAToolFrame
    aBlock
    BlockClosure [] in Seaside.WASessionContinuation>>updateRoot:
  21. thisContext
    optimized [] in Seaside.WAComponent>>visiblePresentersDo:
    self
    BlockClosure [] in Seaside.WAComponent>>visiblePresentersDo:
    ea
    a Seaside.WAToolFrame
    aBlock
    BlockClosure [] in Seaside.WASessionContinuation>>updateRoot:
  22. thisContext
    Seaside.WAToolFrame(Seaside.WAComponent)>>decorationChainDo:
    self
    a Seaside.WAToolFrame
    aBlock
    BlockClosure [] in Seaside.WAComponent>>visiblePresentersDo:
  23. thisContext
    Seaside.WAToolFrame(Seaside.WAComponent)>>visiblePresentersDo:
    self
    a Seaside.WAToolFrame
    aBlock
    BlockClosure [] in Seaside.WASessionContinuation>>updateRoot:
  24. thisContext
    Seaside.WARenderContinuation(Seaside.WASessionContinuation)>>updateRoot:
    self
    a Seaside.WARenderContinuation
    aHtmlRoot
    a Seaside.WAHtmlRoot
  25. thisContext
    Seaside.WARenderContinuation>>newHtmlRoot
    self
    a Seaside.WARenderContinuation
    htmlRoot
    a Seaside.WAHtmlRoot
  26. thisContext
    Seaside.WARenderContinuation>>processRendering:
    self
    a Seaside.WARenderContinuation
    aResponse
    a Seaside.WAResponse 200
    document
    a Seaside.WAHtmlStreamDocument
    htmlRoot
    nil

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Rick Flower
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Issue with moving from Seaside 2.6 to 2.8...

Rick Flower
On Wed, June 11, 2008 7:18 am, Boris Popov wrote:
> Never mind, sorry, didn't scroll far enough. That looks like the problem
> that was fixed a while ago, I would load the latest from public repository
> and check again.

Boris --

I picked the latest version out of the Cincom repository last night (rev
541 if I recall) of the vanilla "Seaside" bundle.. Is the fix not in that
version? Thx!


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Boris Popov, DeepCove Labs (SNN)
Reply | Threaded
Open this post in threaded view
♦
♦
|

RE: Issue with moving from Seaside 2.6 to 2.8...

Boris Popov, DeepCove Labs (SNN)
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
ipAddressString.
 [ ... 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.

Cheers,

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

> -----Original Message-----
> From: [hidden email] [mailto:seaside-
> [hidden email]] On Behalf Of Rick Flower
> Sent: Wednesday, June 11, 2008 9:00 AM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Issue with moving from Seaside 2.6 to 2.8...
>
> On Wed, June 11, 2008 7:18 am, Boris Popov wrote:
> > Never mind, sorry, didn't scroll far enough. That looks like the
problem
> > that was fixed a while ago, I would load the latest from public
> repository
> > and check again.
>
> Boris --
>
> I picked the latest version out of the Cincom repository last night
(rev
> 541 if I recall) of the vanilla "Seaside" bundle.. Is the fix not in
that
> version? Thx!
>
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Rick Flower
Reply | Threaded
Open this post in threaded view
♦
♦
|

RE: Issue with moving from Seaside 2.6 to 2.8...

Rick Flower
Thanks Boris.. I'll give it a shot tonight!

On Wed, June 11, 2008 9:09 am, 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
> ipAddressString.
>  [ ... 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.
>
> Cheers,
>
> -Boris
>
> --
> +1.604.689.0322
> DeepCove Labs Ltd.
> 4th floor 595 Howe Street
> Vancouver, Canada V6C 2T5
> http://tinyurl.com/r7uw4
>
> [hidden email]
>
> CONFIDENTIALITY NOTICE
>
> This email is intended only for the persons named in the message
> header. Unless otherwise indicated, it contains information that is
> private and confidential. If you have received it in error, please
> notify the sender and delete the entire message including any
> attachments.
>
> Thank you.
>
>> -----Original Message-----
>> From: [hidden email] [mailto:seaside-
>> [hidden email]] On Behalf Of Rick Flower
>> Sent: Wednesday, June 11, 2008 9:00 AM
>> To: Seaside - general discussion
>> Subject: Re: [Seaside] Issue with moving from Seaside 2.6 to 2.8...
>>
>> On Wed, June 11, 2008 7:18 am, Boris Popov wrote:
>> > Never mind, sorry, didn't scroll far enough. That looks like the
> problem
>> > that was fixed a while ago, I would load the latest from public
>> repository
>> > and check again.
>>
>> Boris --
>>
>> I picked the latest version out of the Cincom repository last night
> (rev
>> 541 if I recall) of the vanilla "Seaside" bundle.. Is the fix not in
> that
>> version? Thx!
>>
>>
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
mkobetic-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Issue with moving from Seaside 2.6 to 2.8...

mkobetic-2
In reply to this post by Boris Popov, DeepCove Labs (SNN)
Yup, sorry about the delay. Created AR#54545: "WASessionProtector needs the SeasideRequest to provide #remoteAddress"
for this. Should have an "official" fix shortly.

Martin

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
> ipAddressString.
>  [ ... 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.
>
> Cheers,
>
> -Boris
>

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Boris Popov, DeepCove Labs (SNN)
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Issue with moving from Seaside 2.6 to 2.8...

Boris Popov, DeepCove Labs (SNN)
In reply to this post by Boris Popov, DeepCove Labs (SNN)
Re: [Seaside] Issue with moving from Seaside 2.6 to 2.8...

Thank you. I'm not sure if my fix is really a fix, but it was the least intrusive override I could find.

Cheers!

-Boris (via BlackBerry)

----- Original Message -----
From: [hidden email] <[hidden email]>
To: Seaside - general discussion <[hidden email]>
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.

Martin

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
> ipAddressString.
>  [ ... 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.
>
> Cheers,
>
> -Boris
>

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Rick Flower
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Issue with moving from Seaside 2.6 to 2.8...

Rick Flower
In reply to this post by Boris Popov, DeepCove Labs (SNN)
Boris --

I tried this and I don't appear to have any message "ipAddressString"  
in my image.. Also,
what is the local "wsResponse" variable for -- I didn't see it  
referenced anywhere.  Thx!

Below is my current cut at things and it doesn't appear to be very  
happy:

doTheWorkFor: aTransport

        | waHandler waRequest wsResponse |
        waRequest := message.
        waRequest headers at: 'x-forwarded-for' put: aTransport id  
ipAddressString.
        waHandler := aTransport marshaler handlerForRequest: waRequest.
        ^aTransport useStreaming
[ ... ]


-- Rick

On Jun 11, 2008, at 9:09 AM, 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
> ipAddressString.
> [ ... 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.
>
> Cheers,
>
> -Boris
>
> --
> +1.604.689.0322
> DeepCove Labs Ltd.
> 4th floor 595 Howe Street
> Vancouver, Canada V6C 2T5
> http://tinyurl.com/r7uw4
>
> [hidden email]
>
> CONFIDENTIALITY NOTICE
>
> This email is intended only for the persons named in the message
> header. Unless otherwise indicated, it contains information that is
> private and confidential. If you have received it in error, please
> notify the sender and delete the entire message including any
> attachments.
>
> Thank you.
>
>> -----Original Message-----
>> From: [hidden email] [mailto:seaside-
>> [hidden email]] On Behalf Of Rick Flower
>> Sent: Wednesday, June 11, 2008 9:00 AM
>> To: Seaside - general discussion
>> Subject: Re: [Seaside] Issue with moving from Seaside 2.6 to 2.8...
>>
>> On Wed, June 11, 2008 7:18 am, Boris Popov wrote:
>>> Never mind, sorry, didn't scroll far enough. That looks like the
> problem
>>> that was fixed a while ago, I would load the latest from public
>> repository
>>> and check again.
>>
>> Boris --
>>
>> I picked the latest version out of the Cincom repository last night
> (rev
>> 541 if I recall) of the vanilla "Seaside" bundle.. Is the fix not in
> that
>> version? Thx!
>>
>>
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Free forum by Nabble Edit this page