Hi Dan,
I thought it is strange that the setHeadFalse method is setting the
head to true.
Maybe there is a typo there?
regards, aki
2012/3/13 dk...@apache.org:
Author: dkulp
Date: Tue Mar 13 20:34:14 2012
New Revision: 1300342
URL: http://svn.apache.org/viewvc?rev=1300342view=rev
Log:
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
On Wednesday, March 14, 2012 10:09:51 AM Aki Yoshida wrote:
Hi Dan,
I thought it is strange that the setHeadFalse method is setting the
head to true.
Maybe there is a typo there?
Oops. yea. Thanks for spotting that. Was definitely having an I hate
Jetty kind of day. :-(
Dan
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
