Re: Wosid suppression broken in 5.4?
Re: Wosid suppression broken in 5.4?
- Subject: Re: Wosid suppression broken in 5.4?
- From: "Mr. Pierre Frisch" <email@hidden>
- Date: Tue, 18 Dec 2007 18:44:18 -0800
Guido,
The exact behavior is that no session ID is added if either of this is
true:
No session exist before the call (typically a direct action)
or The session id is not stored in the URL (i.e. it is stored in the
cookie)
or There is a binding ?wosid=false
or The query dictionary contains a key wosid bound to Boolean.FALSE
So in the case you mention if the hyperlink is generated in response
to direct action with no session the session ID will not be added to
the URL. If there is a session as it is typical in a component
response page you will get a session ID, this is right if you are
using this to generate internal links and mostly false if you are
generating external links, in those cases you should use the ?
wosid=false binding, which will guarantee that you will never get a
session ID in the URL. Automatically including the session ID prevents
a number of bad behavior where session get recreated when they should
not.
Pierre
--
Pierre Frisch
email@hidden
On Dec 18, 2007, at 18:27, Guido Neitzer wrote:
On 18.12.2007, at 17:04, Mr. Pierre Frisch wrote:
As far as I can see this is a correct behavior even if it is not
what you expected.
Are you sure about that?
If I have (in a clean new application) a hyperlink defined with:
Link : WOHyperlink {
href = href;
}
And the method does this:
public String href () {
return "http://www.apple.com";;
}
It is correct behaviour to get this:
http://www.apple.com/?wosid=yHLPKitjXvvofsyp46dvqg
???
I can understand that when I bind directActionName, or create a
directAction URL or whatever, but adding the session id to something
that is considered a fixed URL?
To quote from the documentation:
"URL to direct the browser to when the link is clicked."
That means a fixed URL for me, not something the framework adds
something at the end. Can you explain a bit more why you think that
is expected behaviour?
And by the way: WO 5.3.3 behaves as I would expect: creating a
hyperlink with just the returned string as the href attribute. I
guess I can file a bug on that one - at least in my opinion, what WO
5.4 does here is absolutely not correct.
cug
--
http://www.event-s.net
--
http://www.event-s.net
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden