Hi all, I have a service that needs to return multiple set-cookie headers back to the requesting browser, but I am only seeing one set-cookie header being returned from apiman. Has anyone else tried this or know of any issues returning multiple headers of the same name but with different values? This multiple set-cookie headers in the response scenario is commonly supported by web servers and browsers. Thanks in advance. Stephen _______________________________________________ Apiman-user mailing list Apiman-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/apiman-user

Incidentally, my reference for that is: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9 and http://www.w3.org/Protocols/rfc2616/rfc2616-sec2.html#sec2 Which I discovered in turn from https://stackoverflow.com/a/4371395 Just asking whether this works for you, because I believe some applications (incorrectly, AFAICT) can't cope with this. On 13 April 2018 at 13:36, Marc Savy <marc.savy(a)redhat.com&gt; wrote: > Hi Stephen, > > Interesting issue. Is this on the Servlet or Vert.x gateway implementation? > > I think we might be able to work around it by appending same-key > values into a single value. > > i.e. > > Foo = Bar > Foo = Baz > > becomes > > Foo = Bar, Baz > > Would that be acceptable for you? > > I'll have to investigate how the underlying platforms handle this > case. I have a vague memory of working on something in this area > before, so I'll have to dig in to see what the state of things is. > > Regards, > Marc > > On 13 April 2018 at 01:31, Stephen Henrie <stephen(a)chassi.com&gt; wrote: >> >> Hi all, >> >> I have a service that needs to return multiple set-cookie headers back to >> the requesting browser, but I am only seeing one set-cookie header being >> returned from apiman. Has anyone else tried this or know of any issues >> returning multiple headers of the same name but with different values? >> >> This multiple set-cookie headers in the response scenario is commonly >> supported by web servers and browsers. >> >> Thanks in advance. >> >> Stephen >> >> >> >> _______________________________________________ >> Apiman-user mailing list >> Apiman-user(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/apiman-user >>

I can now now recall the details on this. In short, this issue is only apparent on the Servlet implementation and should work fine on the Vert.x Gateway. I'll try to fix it for the Servlet implementations, also. I'll report back to this thread shortly. Regards, Marc On 13 April 2018 at 13:38, Marc Savy <marc.savy(a)redhat.com&gt; wrote: > Incidentally, my reference for that is: > > http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9 and > http://www.w3.org/Protocols/rfc2616/rfc2616-sec2.html#sec2 > > Which I discovered in turn from > https://stackoverflow.com/a/4371395 > > Just asking whether this works for you, because I believe some > applications (incorrectly, AFAICT) can't cope with this. > > On 13 April 2018 at 13:36, Marc Savy <marc.savy(a)redhat.com&gt; wrote: >> Hi Stephen, >> >> Interesting issue. Is this on the Servlet or Vert.x gateway implementation? >> >> I think we might be able to work around it by appending same-key >> values into a single value. >> >> i.e. >> >> Foo = Bar >> Foo = Baz >> >> becomes >> >> Foo = Bar, Baz >> >> Would that be acceptable for you? >> >> I'll have to investigate how the underlying platforms handle this >> case. I have a vague memory of working on something in this area >> before, so I'll have to dig in to see what the state of things is. >> >> Regards, >> Marc >> >> On 13 April 2018 at 01:31, Stephen Henrie <stephen(a)chassi.com&gt; wrote: >>> >>> Hi all, >>> >>> I have a service that needs to return multiple set-cookie headers back to >>> the requesting browser, but I am only seeing one set-cookie header being >>> returned from apiman. Has anyone else tried this or know of any issues >>> returning multiple headers of the same name but with different values? >>> >>> This multiple set-cookie headers in the response scenario is commonly >>> supported by web servers and browsers. >>> >>> Thanks in advance. >>> >>> Stephen >>> >>> >>> >>> _______________________________________________ >>> Apiman-user mailing list >>> Apiman-user(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/apiman-user >>>

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

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