Hi Aki
On 14/03/12 11:12, Aki Yoshida wrote:
Hi Sergey,
I am not familiar with this stuff, so what I am saying may not make
sense, though :-)
thanks for the comments, they make sense :-)
But can you use the different default value so that you can
distinguish between the null (i.e.,
One thing I forgot to mention from the start that the easy option is
simply not to attach CrossOriginResourceSharing to a given resource
method, so the filter values will be used instead. I'm only really about
making sure that CrossOriginResourceSharing can still be used if
preferred while
It appears that these 'difficulties' with allowAllOrigins allowOrigins
clearly indicate that the original Benson's idea to get one annotation
per every property in [1] did have a lot of sense, however having the
explosion of annotations seemed too much to me at the time.
That said, I did also
Hi Benson, all,
I've been modifying the CrossOriginResourceSharing annotation as well as
the CrossOriginResourceSharingFilter during the last couple of days to
address the issue reported by Matt Bishop, namely, to do with making it
possible to avoid specifying allowOrigins within the
