From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Ulrich Meis <kenobi(at)halifax(dot)rwth-aachen(dot)de> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: A solution to the SSL customizing problem |
Date: | 2004-10-15 05:28:02 |
Message-ID: | 416F5FE2.1040402@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Ulrich Meis wrote:
> On Friday 15 October 2004 05:35, Oliver Jowett wrote:
>>This doesn't look right, what is '&urlServer&'?
>>
>>>+ Object[] args = { info.getProperty("&urlServer&"),
>>>info.getProperty("sslfactoryargs") };
>
> In parseURL I added a line to set that property to the connection url string
> without parameters. It's the easiest way I am aware of to get the exact url
> down to makeSSL. Since parseURL simply splits parameters upon & and doesn't
> convert escaped &s, I used the &s to make absolutely sure that this property
> never clashes with a real url parameter - also that wouldn't actually matter.
> If nothing else, it makes it obvious that this is internal.
Ouch, that's a bit nasty.
Why exactly would a SSLSocketFactory implementation need to know the
original URL?
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Schaber | 2004-10-15 11:37:35 | Re: A solution to the SSL customizing problem |
Previous Message | Ulrich Meis | 2004-10-15 04:48:03 | Re: A solution to the SSL customizing problem |