From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: AWS SOAP with SSL Date: Tue, 22 May 2018 20:21:56 +0200 Organization: Aioe.org NNTP Server Message-ID: References: NNTP-Posting-Host: CvkHMVp693S8Z+lk11jyqg.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 Content-Language: en-US X-Notice: Filtered by postfilter v. 0.8.3 Xref: reader02.eternal-september.org comp.lang.ada:52587 Date: 2018-05-22T20:21:56+02:00 List-Id: On 2018-05-22 20:07, Björn Lundin wrote: > On 2018-05-22 19:50, Dmitry A. Kazakov wrote: >> On 2018-05-22 19:44, Björn Lundin wrote: >> >>> most likely by compiling AWS with SSL enabled (is not by default) >>> and then use https for urls >> >> Out of curiosity. How can it be default or not? Sometimes you need >> secure, sometimes plain HTTP, on both sides. > > Hmm I don't get the question. AWS (as bundled with compiler) > can do http calls (the client), but not https - raises 'not implemented' > or someting like that. > > recompile it with ssl enabled, and you can use http and https from client. That answers the question. "SSL enabled" = can both HTTP and HTTPS. Default is only HTTP. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de