<div dir="ltr"><div><div><div>Sweet. Thanks for the update.<br><br></div>Will this end up in a 1.3.2.Final version or something else?<br><br></div>Thanks<br></div>Stephen<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 13, 2018 at 12:10 PM, Marc Savy <span dir="ltr"><<a href="mailto:marc.savy@redhat.com" target="_blank">marc.savy@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Stephen,<br>
<br>
I've made a PR that I believe addresses this:<br>
<a href="https://github.com/apiman/apiman/pull/658" rel="noreferrer" target="_blank">https://github.com/apiman/<wbr>apiman/pull/658</a><br>
<br>
Will be merged shortly unless anyone finds issues with it.<br>
<br>
Regards,<br>
Marc<br>
<br>
On 13 April 2018 at 15:10, Marc Savy <<a href="mailto:marc.savy@redhat.com">marc.savy@redhat.com</a>> wrote:<br>
> I can now now recall the details on this.<br>
><br>
> In short, this issue is only apparent on the Servlet implementation<br>
> and should work fine on the Vert.x Gateway.<br>
><br>
> I'll try to fix it for the Servlet implementations, also.<br>
><br>
> I'll report back to this thread shortly.<br>
><br>
> Regards,<br>
> Marc<br>
><br>
> On 13 April 2018 at 13:38, Marc Savy <<a href="mailto:marc.savy@redhat.com">marc.savy@redhat.com</a>> wrote:<br>
>> Incidentally, my reference for that is:<br>
>><br>
>> <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9" rel="noreferrer" target="_blank">http://www.w3.org/Protocols/<wbr>rfc2616/rfc2616-sec14.html#<wbr>sec14.9</a> and<br>
>> <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec2.html#sec2" rel="noreferrer" target="_blank">http://www.w3.org/Protocols/<wbr>rfc2616/rfc2616-sec2.html#sec2</a><br>
>><br>
>> Which I discovered in turn from<br>
>> <a href="https://stackoverflow.com/a/4371395" rel="noreferrer" target="_blank">https://stackoverflow.com/a/<wbr>4371395</a><br>
>><br>
>> Just asking whether this works for you, because I believe some<br>
>> applications (incorrectly, AFAICT) can't cope with this.<br>
>><br>
>> On 13 April 2018 at 13:36, Marc Savy <<a href="mailto:marc.savy@redhat.com">marc.savy@redhat.com</a>> wrote:<br>
>>> Hi Stephen,<br>
>>><br>
>>> Interesting issue. Is this on the Servlet or Vert.x gateway implementation?<br>
>>><br>
>>> I think we might be able to work around it by appending same-key<br>
>>> values into a single value.<br>
>>><br>
>>> i.e.<br>
>>><br>
>>> Foo = Bar<br>
>>> Foo = Baz<br>
>>><br>
>>> becomes<br>
>>><br>
>>> Foo = Bar, Baz<br>
>>><br>
>>> Would that be acceptable for you?<br>
>>><br>
>>> I'll have to investigate how the underlying platforms handle this<br>
>>> case. I have a vague memory of working on something in this area<br>
>>> before, so I'll have to dig in to see what the state of things is.<br>
>>><br>
>>> Regards,<br>
>>> Marc<br>
>>><br>
>>> On 13 April 2018 at 01:31, Stephen Henrie <<a href="mailto:stephen@chassi.com">stephen@chassi.com</a>> wrote:<br>
>>>><br>
>>>> Hi all,<br>
>>>><br>
>>>> I have a service that needs to return multiple set-cookie headers back to<br>
>>>> the requesting browser, but I am only seeing one set-cookie header being<br>
>>>> returned from apiman. Has anyone else tried this or know of any issues<br>
>>>> returning multiple headers of the same name but with different values?<br>
>>>><br>
>>>> This multiple set-cookie headers in the response scenario is commonly<br>
>>>> supported by web servers and browsers.<br>
>>>><br>
>>>> Thanks in advance.<br>
>>>><br>
>>>> Stephen<br>
>>>><br>
>>>><br>
>>>><br>
>>>> ______________________________<wbr>_________________<br>
>>>> Apiman-user mailing list<br>
>>>> <a href="mailto:Apiman-user@lists.jboss.org">Apiman-user@lists.jboss.org</a><br>
>>>> <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/apiman-user</a><br>
>>>><br>
</blockquote></div><br></div>