It can also be done with s_client, just include the encoded username
and password in the appropriate HTTP/1.1 headers supplied as input
to s_client, then look at the HTTP/1.1 headers and other data in the
output from s_client.
On 23/04/2017 04:42, warron.french wrote:
I know that this is a TLS related question; however, do you know how
you can diagnose straight HTTP using:
*telnet */*server1 portnumber* ?/
Then provide HTTP/1.1 etc....?
Is it possible to do the same thing with: *openssl s_client
server1:portnumber* then do the HTTP/1.1 etc... etc...?
Is that a possible technique? I am interested in learning too?
On Fri, Apr 21, 2017 at 6:29 PM, Salz, Rich via openssl-users
<openssl-users@xxxxxxxxxxx <mailto:openssl-users@xxxxxxxxxxx>> wrote:
>https://username:password@xxxxxxxxxx
<https://username:password@xxxxxxxxxx>
> How do I specify this username and password when using
SSL_connect()?
You don't. That stuff is at the protocol level about TLS/SSL.
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
