nday, July 19, 2021 at 4:24 AM
To: "users@qpid.apache.org"
Subject: Re: [Broker-J] Http management interface should ignore OPTIONS method
Hi Tom,
The Qpid Broker-J supports configuring CORS settings to allow access
to REST API from different origins. This can be done via HTT
Hi Tom,
The Qpid Broker-J supports configuring CORS settings to allow access
to REST API from different origins. This can be done via HTTP
management attributes
(corsAllowOrigins,corsAllowMethods,corsAllowHeaders,corsAllowCredentials).
Though, by default, the origin(s), allowed headers and methods
gt; Reply-To: "users@qpid.apache.org"
> Date: Thursday, July 15, 2021 at 10:50 AM
> To: "users@qpid.apache.org"
> Subject: Re: [Broker-J] Http management interface should ignore OPTIONS
> method
>
> Sadly options request is necessary for browsers to assert whe
/Preflight_request)?
I didn’t think it did, but I certainly could be wrong.
--
Tom
From: Mantas Gridinas
Reply-To: "users@qpid.apache.org"
Date: Thursday, July 15, 2021 at 10:50 AM
To: "users@qpid.apache.org"
Subject: Re: [Broker-J] Http management interface should ignore O
Sadly options request is necessary for browsers to assert whether or not
the result of a request should be exposed to caller, isn't it?
On Thu, Jul 15, 2021, 17:47 Tom Jordahl wrote:
> Hello Devs,
>
> In our environment we run security scanning tools. They flag any HTTP
> port that supports the
e some time.
>
> Thanks,
> Olivier
>
> -Original Message-
> From: Rob Godfrey
> Sent: mercredi 29 août 2018 17:58
> To: users@qpid.apache.org
> Subject: Re: [Broker-J] HTTP management
>
> On Wed, 29 Aug 2018 at 17:21, VERMEULEN Olivier
> wrote:
>
> > He
août 2018 17:58
To: users@qpid.apache.org
Subject: Re: [Broker-J] HTTP management
On Wed, 29 Aug 2018 at 17:21, VERMEULEN Olivier
wrote:
> Hello,
>
> While working with the Broker-J HTTP management I found some strange
> behaviors, especially while binding a queue to an exchange.
On Wed, 29 Aug 2018 at 17:21, VERMEULEN Olivier
wrote:
> Hello,
>
> While working with the Broker-J HTTP management I found some strange
> behaviors, especially while binding a queue to an exchange.
>
> * If the exchange does not exist the creation of the binding returns
> 404 where I would e
