Hi Devs, Implementations is completed. I tested few scenarios and it works fine. I will attach the patch to the ticket once the tests and documentations is completed.
Thanks, Asanka On Tue, Jul 14, 2015 at 8:56 AM, Asanka Dissanayake <[email protected]> wrote: > Hi sagara, > Thanks for the input. Implementation is completed. I am working on > testing. I will make the change as you suggested.(servlet transport). > > Thanks, > Asanka D > > On Tuesday, July 14, 2015, Sagara Gunathunga <[email protected]> > wrote: > >> >> Please note Axis2 simple HTTP server is not production recommended hence >> this feature should support Servlet transport in order to support >> production use cases. >> >> Sometimes back I tested cors-filter[1] for Servlet transport >> successfully, I doubt whether we should implement CORS support again or we >> just need to integrate existing implementation such as cors-filter[1]. >> >> >> >> [1] - http://software.dzhuvinov.com/cors-filter.html >> >> Thanks ! >> >> On Mon, Jul 13, 2015 at 6:27 AM, Asanka Dissanayake <[email protected]> >> wrote: >> >>> Hi Devs, >>> What is the best place to implement this. IMHO I think following place >>> is suitable. >>> >>> org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(final >>> AxisHttpConnection conn, final HttpContext context) >>> throws IOException, HttpException >>> >>> Thanks, >>> Asanka D >>> >>> On Sat, Jul 11, 2015 at 3:18 PM, Asanka Dissanayake <[email protected] >>> > wrote: >>> >>>> Yes, agreed. I will start implementation with axis2 http transport . >>>> >>>> Thanks, >>>> Asanka D >>>> >>>> >>>> On Saturday, July 11, 2015, Hiranya Jayathilaka <[email protected]> >>>> wrote: >>>> >>>>> >>>>> On Jul 10, 2015, at 6:50 PM, Asanka Dissanayake <[email protected]> >>>>> wrote: >>>>> >>>>> Hi Devs, >>>>> How about implementing this as an Axis2 module. That will allow user >>>>> to have the feature if user prefers. And we can re-use it for synapse as >>>>> well. >>>>> >>>>> >>>>> I read about this technology a little bit. My preference is for >>>>> implementing it in the HTTP transport. This really is a HTTP-specific >>>>> feature, and I don't see a reason why it should be implemented outside the >>>>> transport. Unfortunately, however, this means we have to re-implement it >>>>> for Synapse. >>>>> >>>>> Thanks, >>>>> Hiranya >>>>> >>>>> >>>>> Thanks, >>>>> Asanka >>>>> >>>>> On Fri, Jul 10, 2015 at 12:46 AM, Hiranya Jayathilaka < >>>>> [email protected]> wrote: >>>>> >>>>>> This might be a useful feature addition to Synapse as well. When >>>>>> you're done with the Axis2 implementation, perhaps you can take a look at >>>>>> the Synapse pass-thru transport as well. >>>>>> >>>>>> Thanks, >>>>>> Hiranya >>>>>> >>>>>> On Jul 9, 2015, at 5:27 AM, T. Allen <[email protected]> wrote: >>>>>> >>>>>> +1 for adding CORS support. >>>>>> >>>>>> >>>>>> On 7/8/2015 8:13 PM, Asanka Dissanayake wrote: >>>>>> >>>>>> Hi Devs, >>>>>> I recently happened to call a Axis2Service with AJAX post method. >>>>>> Then there was an "Access-Control-Allow-Origin Error". When I was digging >>>>>> through the path, I came to know about CORS (Cross Origin Resource >>>>>> Sharing) >>>>>> spec [1] . >>>>>> >>>>>> User agents commonly apply same-origin restrictions to network >>>>>> requests. These restrictions prevent a client-side Web application >>>>>> running >>>>>> from one origin from obtaining data retrieved from another origin, and >>>>>> also >>>>>> limit unsafe HTTP requests that can be automatically launched toward >>>>>> destinations that differ from the running application's origin. >>>>>> >>>>>> To overcome this issue , I implemented an axis2 handler which the >>>>>> implementation is very specific to my use case. It handles the preflight >>>>>> request. >>>>>> >>>>>> In Axis2 , have we implemented CORS Spec? If not what about providing >>>>>> CORS support with Axis2? >>>>>> Since I already have the implementation, I can make it more generic >>>>>> and add to Axis2. >>>>>> >>>>>> [1] http://www.w3.org/TR/cors/ >>>>>> >>>>>> Thanks, >>>>>> Asanka >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>>> >>>>>> -- >>>>>> Hiranya Jayathilaka >>>>>> Mayhem Lab/RACE Lab; >>>>>> Dept. of Computer Science, UCSB; http://cs.ucsb.edu >>>>>> E-mail: [email protected]; Mobile: +1 (805) 895-7443 >>>>>> Blog: http://techfeast-hiranya.blogspot.com >>>>>> >>>>>> >>>>> >>>>> -- >>>>> Hiranya Jayathilaka >>>>> Mayhem Lab/RACE Lab; >>>>> Dept. of Computer Science, UCSB; http://cs.ucsb.edu >>>>> E-mail: [email protected]; Mobile: +1 (805) 895-7443 >>>>> Blog: http://techfeast-hiranya.blogspot.com >>>>> >>>>> >>> >> >> >> -- >> Sagara Gunathunga >> >> Blog - http://ssagara.blogspot.com >> Web - http://people.apache.org/~sagara/ >> LinkedIn - http://www.linkedin.com/in/ssagara >> >
