Have you tried amqps:/example.xyz.com or even example.xyz.com:5671?
On Fri, Jun 25, 2021 at 2:43 PM rahul.sin...@morganstanley.com
<rahul.sin...@morganstanley.com> wrote:
>
> Hello,
> I get below exception -
> Caught std::exception Invalid URL: amqps://example.xyz.com
> (qpid/qpid-cpp-1.39.0/src/qpid/Url.cpp:248)
>
> We have been by the broker at the other end that fully qualified domain names
> are necessary for certificate handshake.
>
> Best Regards,
> Rahul
> -----Original Message-----
> From: Gordon Sim <g...@redhat.com>
> Sent: 25 June 2021 11:40
> To: users@qpid.apache.org
> Subject: Re: QPID C++ Connection url
>
> On Fri, Jun 25, 2021 at 9:50 AM rahul.sin...@morganstanley.com
> <rahul.sin...@morganstanley.com> wrote:
> > The Apache QPID C++ Messaging library states the below rule for url
> >
> > /** Simple recursive-descent parser for this grammar:
> > url = ["amqp:"][ user ["/" password] "@" ] protocol_addr *(","
> > protocol_addr) protocol_addr = tcp_addr / rmda_addr / ssl_addr / ..
> > others plug-in tcp_addr = ["tcp:"] host [":" port] rdma_addr = "rdma:"
> > host [":" port] ssl_addr = "ssl:" host [":" port] */
> >
> > However, the broker at the other end of our communication channel expects
> > the URL to have the fully qualified domain names for certificate handshake.
> > Their expectation is to see url in this pattern - amqps://example.xyz.com,
> > where //example.xyz.com corresponds to the host and port.
> > However, when I try to use this pattern, I receive incorrect URL exception.
>
> Not sure what you are seeing. However you can just use host:port (which is
> generally what I do as I find it simpler). There should certainly be no issue
> with fully qualified hostnames either way though.
>
> > Secondly, is there a way we can specify the interface through which the
> > host and port connection will go out.
>
> I'm not sure I understand. The hostname will resolve to an ip address and the
> normal routing should then determine how to direct the packets.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional
> commands, e-mail: users-h...@qpid.apache.org
>
>
> --------------------------------------------------------------------------------
> NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions
> or views contained herein are not intended to be, and do not constitute,
> advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform
> and Consumer Protection Act. If you have received this communication in
> error, please destroy all electronic and paper copies and notify the sender
> immediately. Mistransmission is not intended to waive confidentiality or
> privilege. Morgan Stanley reserves the right, to the extent permitted under
> applicable law, to monitor electronic communications. This message is subject
> to terms available at the following link:
> http://www.morganstanley.com/disclaimers If you cannot access these links,
> please notify us by reply message and we will send the contents to you. By
> communicating with Morgan Stanley you consent to the foregoing and to the
> voice recording of conversations with personnel of Morgan Stanley.
>
> You may have certain rights regarding the information that Morgan Stanley
> collects about you. Please see our Privacy Pledge
> https://www.morganstanley.com/privacy-pledge for more information about your
> rights.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
