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: 
 border1.nntp.dca3.giganews.com!backlog3.nntp.dca3.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!news.snarked.org!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Natasha Kerensikova <lithiumcat@instinctive.eu>
Newsgroups: comp.lang.ada
Subject: Re: AWS and "304 Not Modified" responses
Date: Fri, 28 Mar 2014 15:01:48 +0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <slrnljb3m6.i0l.lithiumcat@nat.rebma.instinctive.eu>
References: <slrnlj889j.i0l.lithiumcat@nat.rebma.instinctive.eu>
 <1395938603.714.0.camel@pascal.home.net>
Injection-Date: Fri, 28 Mar 2014 15:01:48 +0000 (UTC)
Injection-Info: mx05.eternal-september.org;
 posting-host="76a49b86bc3e16725b7cfca3d85cb4c8";
 logging-data="5345"; mail-complaints-to="abuse@eternal-september.org";
 posting-account="U2FsdGVkX1/4DsLp44g9s3LHlMXlHuUs"
User-Agent: slrn/1.0.1 (FreeBSD)
Cancel-Lock: sha1:6hZG6zYKdWsLHFAenx9fuJfFMhw=
X-Original-Bytes: 1992
Xref: number.nntp.dca.giganews.com comp.lang.ada:185396
Date: 2014-03-28T15:01:48+00:00
List-Id: <comp.lang.ada>

Hello,

On 2014-03-27, Pascal Obry <pascal@obry.net> wrote:
>> Am I missing something or is it really impossible?
>
> AWS.Response.Set.Add_Header.
>

Indeed, that's exactly what I needed, thanks a lot.

It seems I missed it because I went through code only with specific
grep, which doesn't return general functions like this Add_Header. I
then used the documentation at http://docs.adacore.com/aws-docs/aws/
I was clear from the structure that I needed something in AWS.Response
or one of its children, but chapter 13 doesn't list any child, hence my
asking here.

This raises the question, why is there no mention of AWS.Response.Set in
the documentation? (except for a single occurrence of
AWS.Reponse.Set.Clear_Session in a comment).
Is it the documentation lagging behind a new feature?
Or is AWS.Response.Set part of internal facilities that aren't covered
by the implicit stability promises of documented API?


Thanks again for the help,
Natasha