Hi Benson
On 02/12/11 22:16, Benson Margulies wrote:
On Fri, Dec 2, 2011 at 4:45 PM, Sergey Beryozkinsberyoz...@gmail.com wrote:
Hi Benson
I think we should get rid of that Class level annotation that you
introduced. It is not secure enough - the path and verb values it lists -
they can not
On Thu, Dec 1, 2011 at 10:34 AM, Sergey Beryozkin sberyoz...@gmail.com wrote:
On 01/12/11 14:51, Benson Margulies wrote:
I propose to add the following
@CorsAllowAllOrigins
@CorsAllowOrigins( origin1., ... originN )
@CorsAllowMethods( meth1 ... methn )
@CorsExposeMethods( ... )
Sergey,
I've hit a snag with preflight. In preflight, the client sends an
OPTIONS with a 'requestMethod' and we have to decide if we like that
method. This is section 6.1.5.
The client sends OPTIONS with the method, a list of custom headers,
and of course the full URL.
I need to map that to the
I forgot to ask, can you help me figure out which class is the right
class for the information I've got?
Hi Benson
On 01/12/11 18:36, Benson Margulies wrote:
Sergey,
I've hit a snag with preflight. In preflight, the client sends an
OPTIONS with a 'requestMethod' and we have to decide if we like that
method. This is section 6.1.5.
The client sends OPTIONS with the method, a list of custom
