On May 6, 2009, at 11:36 AM, Mr. Pierre Frisch wrote: Item 3 Can you elaborate on the wrong server name? Thanks
Hi Pierre,
Thanks for your response.
Regarding item #3 - "The generated direct action URL has the wrong server name" :
The situation is as follows, when the application is deployed it is accessed securely with a URL that begins with https://www.mpv.com/app/WebObjects/...[ etc]...
Now, the URLs generated by calling the directActionURLForActionNamed(String,NSDictionary) method have a server name of web1-bu instead of www.mpv.com. In other words, the URLs looked something like this:
http://web1-bu/app/WebObjects/OurApp.woa/1/wa/MPVAjaxAction/MPVContractPicker?wosid=vh5ESREs0GHHbDbjIkwTGw
Notice web1-bu as the server name in that URL instead of the expected www.mpv.com. I could not figure out where that was coming from so I started inspecting the HTTP request headers to see if that server name was present anywhere. That's where I found a server_name header with a value of web1-bu. So I'm suspecting WO is simply looking at different things to determine the server name and that it might have picked up the server name from the server_name HTTP request header. Here are the list of HTTP request headers from the application:
We looked at the configuration files for Apache on Solaris which is our web server and in particular we looked at the httpd.conf file and the sslInclude.conf file which is included from httpd.conf. But we still can't figure out why server_name has a value of web1-bu. :-/
Now, the other question I have is this: is it mandatory that we upgrade Apache and the WebObjects adaptor in order to deploy our WO 5.4.3 application? Or can we still use Apache 1.3.9 and its corresponding WebObjects adaptor for our WO 5.4.3 application?
Thanks a million,
Ricardo J. Parada Medical Present Value, Inc.
|