http - CORS Java server side implementation -


i need implement cors support in jersey based rest server. i've gone through of available material , informative tutorials . found 2 approaches people using:

approach-1 :

simple , direct approach implement 1 http filter adds cors header response (jersey specific)

public class responsecorsfilter implements containerresponsefilter {  public containerresponse filter(containerrequest req, containerresponse contresp) {          responsebuilder resp = response.fromresponse(contresp.getresponse());         resp.header("access-control-allow-origin", "*")                 .header("access-control-allow-methods", "get, post, options");          string reqhead = req.getheadervalue("access-control-request-headers");          if(null != reqhead && !reqhead.equals(null)){             resp.header("access-control-allow-headers", reqhead);         }          contresp.setresponse(resp.build());             return contresp;     } }

approach-2 :

fully implement cors per specification i.e. preflight request handling , header support. inspected source code of 1 such open-source java implementation cors-filter

my question approach should taken when? downside of approach-1 vs approach-2?

my use case origins/methods can allowed , authorization http header part of rest requests. inclined towards approach-1 seems of default cors settings suffice use case not sure if not having full cors specs implemented @ server side create issues whatsoever.

for purposes, approach #1 sounds sufficient. approach #2 more case have different responses based on request type, or want validate request information. if response same across request types, #1 should fine. note because implementation allowing requests succeed, should doing own checks make sure request valid. since allowing authorization header, i'm assuming aware of this, , validating authorization token?


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers ...
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());...
Read more