Hello Marc,
I don't think the problem is associated with *Access-Control-Allow-Origin*.
Below there are two requests using Restlet Client, the first one works
without the *Header Access-Controle-Request-Method*, the second only adding
this Header gets fail.
[image: image.png]
On Tue, 18 Dec 2018 at 09:40, Marc Savy <marc.savy(a)redhat.com> wrote:
I think your issue might be the way that you're formulating your
request.
In order to issue a valid CORS request, you must set your origin header.
You should probably try that first.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Origin
e.g. curl ... -H "Origin: mymachine.local"
When using a browser, this is usually issued on your behalf. But, if
you're using curl, it won't be.
On Tue, 18 Dec 2018 at 12:35, Renato Barros <renalexster(a)gmail.com> wrote:
> Hi Marc,
>
> I've just updated the image with details. The Access-Control-Allow-Origin
> already had "*" as value.
>
> [image: image.png]
>
> On Tue, 18 Dec 2018 at 05:50, Marc Savy <marc.savy(a)redhat.com> wrote:
>
>> I'm not sure why your browser isn't rendering it, but there should be a
>> list in the Access-Control-Allow-Origin section that would allow you to add
>> an entry such as "*" or "foo.com".
>>
>> What is your setup?
>>
>> On Mon, 17 Dec 2018 at 19:10, Renato Barros <renalexster(a)gmail.com>
>> wrote:
>>
>>> Hello all,
>>>
>>> I'm getting an error with *Access-Control-Request-Method* Header in my
>>> APIs.
>>>
>>> I posted details in StackOverflow
>>>
<
https://stackoverflow.com/questions/53821510/apiman-return-error-400-for-...
>>> .
>>>
>>> Please, someone could help me?
>>> _______________________________________________
>>> Apiman-user mailing list
>>> Apiman-user(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/apiman-user
>>>
>>