• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Secure WOHyperlink puts :443 in URL
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Secure WOHyperlink puts :443 in URL


  • Subject: Re: Secure WOHyperlink puts :443 in URL
  • From: Chuck Hill <email@hidden>
  • Date: Fri, 11 Jun 2004 07:36:10 -0700

Better late than never...

The :443 is a defect/artifact of they way that WO generates URL. This will appear wheneven you set the secure binding of a WOHyperlink to true. For Even more fun, set it to false. WO will generate the extremely helpful URL
http://www.domain.com:443
Yeah, nice QA process. You can fix the above problem by creating a WOContext sub-class and overriding this method:
public String completeURLWithRequestHandlerKey(String requestHandlerKey,
String requestHandlerPath,
String queryString,
boolean isSecure,
int somePort) {
return super.completeURLWithRequestHandlerKey(requestHandlerKey,
requestHandlerPath, queryString, isSecure, isSecure ? 443 : 80);
}


This however, won't fix your :443 problem. To do that you will need to do one of:
- generate your own URL and bind to the href of WOHyperlink
- replace/repair the WOContext method completeURLWithRequestHandlerKey
- replace/repair the WORequest method _completeURLPrefix (danger! private API!)


Chuck


On Jun 9, 2004, at 10:00 PM, Marek Wawrzyczny wrote:

We are using 443 - standard SSL port... but we are running multiple IPs...
Still as far as WO works it shouldn't matter, should it.


Actually, we just got an error report from our users that the site breaks under https on IE 5 on OS X and Opera (on OS X only?). On IE we get an error whenever trying to view secure content:

"Security failure. Data encryption error."

So this appears to be an Apache problem. Still, can anyone confirm that WO does NOT put the :443 port number on WOHyperlinks bound to DAs with the security binding set to true?

I'd really like to know why we are seeing the ":443" being appended to URLs by WO. Does anyone know when that should happen, and when it should not happen? I suspect that what we are seeing is a side-effect of whatever problem we are having with Apache.



On 09/06/2004, at 15:43, Deirdre Saoirse Moen wrote:

On Jun 8, 2004, at 7:12 PM, Marek Wawrzyczny wrote:

On WO 5.2.3 we are now having a problem where WO puts the port number whenever we set secure to true. Is this the default behaviour or do I have to set something somewhere?

Are you running https on a non-standard port?
--
_Deirdre http://deirdre.net
"Cannot run out of time. There is infinite time. You are finite. Zathras is finite. This....is wrong tool." -- Zathras




Marek Wawrzyczny

software engineer
-------------------------->
ish group pty ltd
http://www.ish.com.au
7 Darghan St Glebe 2037 Australia
phone +61 2 9660 1400 fax +61 2 9660 7400
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >Secure WOHyperlink puts :443 in URL (From: Marek Wawrzyczny <email@hidden>)
 >Re: Secure WOHyperlink puts :443 in URL (From: Deirdre Saoirse Moen <email@hidden>)
 >Re: Secure WOHyperlink puts :443 in URL (From: Marek Wawrzyczny <email@hidden>)

  • Prev by Date: Re: Catching an exception thrown by invalid IP address
  • Next by Date: Re: More Java Than WebObjects
  • Previous by thread: [OT] Re: Secure WOHyperlink puts :443 in URL
  • Next by thread: Re: Secure WOHyperlink puts :443 in URL
  • Index(es):
    • Date
    • Thread