Re: WOHyperlink secure binding and hostname:port problem
Re: WOHyperlink secure binding and hostname:port problem
- Subject: Re: WOHyperlink secure binding and hostname:port problem
- From: "Catarina Simoes" <email@hidden>
- Date: Sun, 14 Sep 2008 18:35:26 +0100
Hi Chuck,
Thanks for your email! :)
I've came across a problem when using the secure WOHyperlink binding. While not using any SSL stuff and with the secure binding binded to false, WebObjects 5.2.2 rather than generating the action link to servername:port (I'm using a port other than 80), it just generates the link to the servername.
Does it work correctly if you manually edit the URL used to first get to the application?
Yes, if I edit the url and add the port number it just works.
Apache is configured to use a non standard port and it seems WebObjects is ignoring that port and using 80.
Am I doing anything wrong in httpd.conf?
Port 8888
Listen 8888
Listen 443
vhost for *:443
Is this a bug?
No, WebObjects does not look at the Apache configuration.
Not even when a WOHyperlink element has a "secure" binding?
Is there any way to force WOHyperlink to generate the link to a predefined server name and port?
Thanks in advance.
The thing is when the binding "secure" is added to the WOHypelink element even if it's set to null, WO seems to completely ignore the port and the generated link has only the server name.
That's why I believe it might be a WO 5.2.2 bug...
Best regards,
Catarina
_______________________________________________
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