Re: [U2] B2B

[Craig Bennett]

Ross,
Ross Ferris wrote:
Secure implies SSL, which as you identify means using well known ports. I'd think it would take a lot more work to bastardise a solution using encrypted traffic on non-standard ports (I don't think you want to encrypt ALL traffic, so 80 won't do the trick) than changing your proxy to include SSL ports
HTTP proxying should work regardless of the proxy port -- you certainly 
can configure a proxy with different ports for http/https but I don't 
believe you need to (the proxy just has to understand the HTTP CONNECT 
method AFIK).

If callHTTP allows you to use a proxy, it should send all traffic there 
regardless of the destination port.

To confirm this was the problem, you could try using callHTTP to access 
a site on some non-standard port (eg: 8080) via the proxy and see if 
that works.

Craig
---
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

[U2] B2B

[Moderator]

Posted for non-member (Colin Lucas (The System Works) [EMAIL PROTECTED]).
We are trying to test a secure B2B  solution from within UV (version 10.0.8
on Unix variant TRU64 5.1b on an Alphaserver ES80) using XML  https. The
internet connection is via a proxy server that only listens for client
connections on port 80. I have used setHTTPDefault to set the address of the
proxy server and the port to 80; amongst other things.
However, when I use submitRequest with a request handle created by a call to
createSecureRequest it is directed to port 443 (SSL) of the proxy server. I
have been able to determine this by using protocol logging and inspecting
httplog. Normal http(80) through the proxy server is not a problem.
Short of re-inventing the wheel and using the direct sockets API, can
anybody shed some light on how to stop submitRequest when seeing https,
deciding it must go to port 443 of the proxy. Unfortunately, due to some
corporate constraints, changing the ports the proxy server listens on is not
a trivial task.  

Thanks,
Colin Lucas
The System Works - Guaranteed
ABN 49 010 514 557
Tel: + 61 7 3394   Fax: + 61 7 3394 0099
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] 
The System Works Pty Ltd - Confidential Communication
The information contained in this email is confidential. Any views or
opinions expressed in this communication are those of the individual sender,
except where the sender specifically states that the views or opinions are
those of The System Works Pty Ltd. This communication is intended to be
solely for the use of the addressee(s) and may contain copyright and / or
legally privileged information. If you receive this email by mistake please
promptly inform us by reply e-mail or telephone (+61 7 3394 ) and then
delete the email and destroy any printed copy. Any unauthorised form or
reproduction of this message is prohibited. As Internet communications are
capable of data corruption, The System Works Pty Ltd does not guarantee the
security of any information electronically transmitted and does not accept
responsibility for any improper or incomplete transmission of the
information contained in this communication, nor for any delay in its
receipt.
---
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

RE: [U2] B2B

[Ross Ferris]

Secure implies SSL, which as you identify means using well known ports. I'd think 
it would take a lot more work to bastardise a solution using encrypted traffic on 
non-standard ports (I don't think you want to encrypt ALL traffic, so 80 won't do the 
trick) than changing your proxy to include SSL ports

Ross Ferris
Stamina Software
Visage  an Evolution in Software Development


-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-u2-
[EMAIL PROTECTED] On Behalf Of Moderator
Sent: Monday, 9 August 2004 10:28 AM
To: U2 Users Discussion List
Subject: [U2] B2B

Posted for non-member (Colin Lucas (The System Works)
[EMAIL PROTECTED]).

We are trying to test a secure B2B  solution from within UV (version 10.0.8
on Unix variant TRU64 5.1b on an Alphaserver ES80) using XML  https. The
internet connection is via a proxy server that only listens for client
connections on port 80. I have used setHTTPDefault to set the address of
the
proxy server and the port to 80; amongst other things.

However, when I use submitRequest with a request handle created by a call
to
createSecureRequest it is directed to port 443 (SSL) of the proxy server. I
have been able to determine this by using protocol logging and inspecting
httplog. Normal http(80) through the proxy server is not a problem.

Short of re-inventing the wheel and using the direct sockets API, can
anybody shed some light on how to stop submitRequest when seeing https,
deciding it must go to port 443 of the proxy. Unfortunately, due to some
corporate constraints, changing the ports the proxy server listens on is
not
a trivial task.

Thanks,

Colin Lucas
The System Works - Guaranteed
ABN 49 010 514 557
Tel: + 61 7 3394   Fax: + 61 7 3394 0099
 mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
The System Works Pty Ltd - Confidential Communication
The information contained in this email is confidential. Any views or
opinions expressed in this communication are those of the individual
sender,
except where the sender specifically states that the views or opinions are
those of The System Works Pty Ltd. This communication is intended to be
solely for the use of the addressee(s) and may contain copyright and / or
legally privileged information. If you receive this email by mistake please
promptly inform us by reply e-mail or telephone (+61 7 3394 ) and then
delete the email and destroy any printed copy. Any unauthorised form or
reproduction of this message is prohibited. As Internet communications are
capable of data corruption, The System Works Pty Ltd does not guarantee the
security of any information electronically transmitted and does not accept
responsibility for any improper or incomplete transmission of the
information contained in this communication, nor for any delay in its
receipt.
---
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/


---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.735 / Virus Database: 489 - Release Date: 6/08/2004


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.735 / Virus Database: 489 - Release Date: 6/08/2004
---
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/