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: Chuck Hill <email@hidden>
- Date: Sun, 14 Sep 2008 14:01:13 -0700
On Sep 14, 2008, at 10:35 AM, Catarina Simoes wrote:
Hi Chuck,
Thanks for your email! :)
Always a pleasure. :-)
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.
Look at this document: http://developer.apple.com/documentation/WebObjects/WOAppProperties/Articles/ApplicationProperties.html#/
/apple_ref/doc/uid/TP40005337-SW1
Setting WOCGIAdaptorURL might solve your problem (or some of it).
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?
No. It _will_ look at the HTTP headers in the request and should be
able to get any needed information from there.
Is there any way to force WOHyperlink to generate the link to a
predefined server name and port?
Thanks in advance.
It should pick up the server name and port form the HTTP headers.
Maybe try setting secure to true? It has been a long time since I
have done this.
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.
I'm not sure what should happen.
If I remove the binding "secure" everything works fine and the link
generated is http://servername:8888/cgi-bin/blablabla
That's why I believe it might be a WO 5.2.2 bug...
Yes, that might be the case. I recall there have been some bugs both
with the secure binding and with changes in the header names.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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