Re: directActionURLForActionNamed produce corrupted hostname
Re: directActionURLForActionNamed produce corrupted hostname
- Subject: Re: directActionURLForActionNamed produce corrupted hostname
- From: Serge Cohen <email@hidden>
- Date: Mon, 7 Jul 2008 01:44:14 +0200
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
My mistake... Indeed this was an error in the setting of the apache
server, producing a SERVER_NAME of ..._copy
This happened when I set the HTTPS part of Apache through ServerAdmin.
Serge.
Le 6 juil. 08 à 00:24, Serge Cohen a écrit :
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello list;
I'm currently working on an application using Wonder (last updated
on 2008-07-01) and WebObjects 5.4 (since few days 5.4.2, but the
problem I'm reporting here was already present in previous version
5.4.1 ... I was just hoping for it to be solved in 5.4.2 until now).
I have a layout page, using a couple of URL to direct actions. I
generate those using the method :
WOContext.directActionURLForActionNamed(String anActionName,
NSDictionary<String,Object> queryDictionary)
(or ERXWOContext.directActionURLForActionNamed(String anActionName,
NSDictionary<String,Object> queryDictionary, boolean
includeSessionID), which directly calls super... implementation)
When pages are sent through 'http' (non-secured), the generated URL
is an absolute path, but no scheme or host.
When pages are sent through 'https', the generated URL are full
URLs, including scheme and hostname.
This is working fine as long as I'm in development setup (Eclipse as
IDE), but as soon as I deploy, when a page is sent through 'https'
the host name gets 'corrupted', more precisely '_copy' is appended
to the host name (whilst, when sent by 'http', the URL are absolute,
withOUT scheme or hostname).
I've even tried to use Eclipse on the same machine that is running
the deployed application : this does not show the behaviour of the
deployed application.
I've also noted the exact same type of problem when using a
WOHyperlink 'connected' to a directAction, with the 'secure' binding
set to false, and the page is sent using 'https'.
Clearly, I don't understand well enough the difference between the
dev. environment and the deployment one (in my case 'classical'
wotaskd/JavaMonitor).
I've reported this bug with ID : 6055888
In the mean time I'd like to be at least able to reproduce this
behaviour when running from Eclipse (to debug and get a better
understanding of what's going wrong) and hopefully a workaround
(which should be possible, given the Dev. environment manages to get
these generated URLs as they should).
Thanks for any insight or help;
Serge.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkhxWM8ACgkQlz6UVQtc2uyKpgCfTd/dfQGSuwUe8ybGjiBSBa66
0PwAoIRWOmGgmKFe6zkdoNpX7Swn3Pr0
=x6qF
-----END PGP 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