<div dir="ltr">1.2.8.Final</div><br><div class="gmail_quote"><div dir="ltr">On Tue, Sep 26, 2017 at 8:04 AM Marc Savy <<a href="mailto:marc.savy@redhat.com">marc.savy@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Scott,<div><br></div><div>Which version of Apiman are you using?</div><div><br></div><div>Regards,</div><div>Marc</div></div><div class="gmail_extra"><br><div class="gmail_quote"></div></div><div class="gmail_extra"><div class="gmail_quote">On 26 September 2017 at 00:10, Scott Elliott <span dir="ltr"><<a href="mailto:scottpelliott@gmail.com" target="_blank">scottpelliott@gmail.com</a>></span> wrote:<br></div></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Why, when the CORS policy plugin is used, do I get multiple Access-Control-Allow-Origin headers in the response. From curl:<div><br></div><div>Origin: <a href="http://blah.com" target="_blank">http://blah.com</a></div><div><br></div><div>Access-Control-Allow-Origin: <a href="http://blah.com" target="_blank">http://blah.com</a></div><div>Access-Control-Allow-Origin: Jetty(9.2.19.v20160908)</div><div><br></div><div>Chrome does not like the multiple headers, so the API request fails.</div><div><br></div><div><br></div><div><div><br></div><div><br></div></div></div>
<br></blockquote></div></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">_______________________________________________<br>
Apiman-user mailing list<br>
<a href="mailto:Apiman-user@lists.jboss.org" target="_blank">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/mailman/listinfo/apiman-user</a><br>
<br></blockquote></div><br></div>
</blockquote></div>