I doubt that you're the only person in the world left using PSP - though
I must admit that I don't use PSP for my own Webware projects (only
plain Webkit). Unfortunately, the orginal developers have long ago
abandoned the PSP project and I'm left alone trying to maintain it
without being an active user.
But anyway, I think PSP is still in a pretty good shape, and I don't
experience the problems you're mentioning.
There is another thing I find somewhat disturbing:
You're saying that you're updating from version 0.9.0. This version is
four years old and there have been versions 0.9.1 to 0.9.4, 1.0 and many
beta and rc versions. So why did you never update before and now expect
that everything goes smoothly and without any compatibility issues?
I have always asked people to check the betas and release candidates,
but the feedback was mostly been disappointing. Open Source software
lives from active participation and feedback of its users. How can it be
improved when there is only feedback every four years?
Anyway, let's try to solve this problem.
> First thing I found out was that self.transaction().hasSession() ALWAYS
> returns False.
This is actually a WebKit method that has nothing to do with PSP and
works fine for me. It's certainly only a subsequent fault of the next
problem you're mentioning.
> And instead of setting the path to "/", the cookie path is set to
> "/path_to/page.psp/" (path_to being the subdir on the server, and the
> / in the end is no typo). So I quickly get a whole bag of cookies but
> no session.
The cookie path is set to the servlet path of the application in newer
versions of Webware, since setting it to "/" can be a security problem.
So for some strange reason, your Webware installation seems to think
"/path_to/page.psp/" is your servlet path.
However, I just tested this, created a PSP page that is using a session,
and for me everything is working fine, with both built-in webserver and
Also note that you can configure the servlet path manually using the
setting SessionCookiePath in Application.config - you can simply set it
to "/" or the root path of your application. This has been properly
documented in the Release Notes and Configuration guide, by the way.
> Anybody doing anything with PSP would have found out about this quickly.
> Since it hasnt been mentioned in weeks, I came to believe I am the last
> person on earth using PSP which makes me feel sort of sad.
You're really too quick to jump to conclusions. As I said it is working
> Also self.request.serverURL() and related methods do now return results
> which are completely different than in my old install (must have been
> around 0.9.0) and they are often wrong. Difference: there is always
> http:// in front which wasnt there before.
> http://doma.in/foo/bar/ -> serverURL() = http://doma.in/
> http://doma.in/foo/bar.psp -> serverURL() = http://doma.in/foo/bar.psp
serverURL() has been adapted a long time ago to include the protocol
because that's sometimes useful to know and because this is what you
expect from a method that has URL in its name.
> As for the other methods, self.response().hostAndPort() for example
> never ever returns a port number when used with mod_webkit2, even though
> the method name implicitly advertises that functionality.
I guess you mean request().hostAndPort() (which is a new method, btw).
The method name shall imply that it returns the host-and-port-section of
the URL which works very well for me. The only thing is that the port
can be missing if it is the default port. I can clarify this in the
> Due to the massive session problem I will now ruefully go back to my
> ancient installation.
Again, so far I don't see any massive problems with Webware 1.0.1, but
only a small API change with serverURL and the unsolved question why you
have the wrong servlet path for PSP. Maybe you have set up some unusual
redirection with Apache or something. What does your Apache config look
like? Also, are you sure you're using mod_webkit2 as adapter?