erlang - Enabling CORS for Cowboy REST API -


how can enable cors cowboy rest handler? tried add options/2 method, this:

options(req, state) ->     {[        {<<"access-control-allow-origin">>, <<"*">>},        {<<"access-control-allow-methods">>, <<"get, options">>}      ], req, state}.

but causes errors like:

error in process <0.263.0> exit value: {{case_clause,{[{<<27 bytes>>,<<1 byte>>},{<<28 bytes>>,<<12 bytes>>}],{http_req,#port<0.2636>,ranch_tcp,keepalive,<0.263.0>,<<7 bytes>>,{1,1},{{127,0,0,1},56522},<<9 bytes>>,undefined,9090,<<8 bytes>>,undefined,<<0 bytes>>,undefined,<<0 bytes>>,[],[{<<4 bytes>>,<<14 bytes>>},{<<10 bytes>>,<<74 bytes>>},{<<6 bytes>>,<<63 bytes>>},{<<15 bytes>>,<<14 bytes>>},{<<15 bytes>>,<<13 bytes>>},{<<6 bytes>>,<<4 bytes>>},{<<29 bytes>>,<<3 bytes>>},{<<30 bytes>>,<<16 bytes>>},{<<10 bytes>>,<<10 bytes>>}],[{<<10 bytes>>,[<<10 bytes>>]}],undefined,[],waiting,undefined,<<0 bytes>>,false,waiting,[],<<0 bytes>>,undefined},undefined...

where mistake?

cowboy documentation says need set header using set_resp_headers, not return list of headers:

 %% if need add additional headers response @ point,  %% should directly in options/2 call using set_resp_headers.

so code should like:

options(req, state) ->     req1 = cowboy_req:set_resp_header(<<"access-control-allow-methods">>, <<"get, options">>, req),     req2 = cowboy_req:set_resp_header(<<"access-control-allow-origin">>, <<"*">>, req1),     {ok, req2, state}.

you can test with

curl -h "origin: http://example.com" \   -h "access-control-request-method: get" \   -h "access-control-request-headers: x-requested-with" \   -x options --verbose \ http://localhost:8080 * connect() localhost port 8080 (#0) *   trying 127.0.0.1... connected * connected localhost (127.0.0.1) port 8080 (#0) > options / http/1.1 > user-agent: curl/7.21.4 (universal-apple-darwin11.0) libcurl/7.21.4 openssl/0.9.8r     zlib/1.2.5 > host: localhost:8080 > accept: */* > origin: http://example.com > access-control-request-method: > access-control-request-headers: x-requested-with > < http/1.1 200 ok < connection: keep-alive < server: cowboy < date: mon, 25 mar 2013 15:59:11 gmt < content-length: 0 < access-control-allow-methods: get, options < access-control-allow-origin: * < * connection #0 host localhost left intact * closing connection #0

Comments

Post a Comment

Popular posts from this blog

authentication - Mongodb revoke acccess to connect test database -

i have ec2 instance mongodb 3.2.0 installed. have user admin access. can connect user , perform operation remotely. 1 can connect database test remote if knows ip mongo 11.11.11.11. although not able make operations, want restrict access user credentials can connect server. first need create users , grant roles users, example: use admin db.createuser( { user: "myuseradmin", pwd: "abc123", roles: [ { role: "useradminanydatabase", db: "admin" } ] } ) then need start server --auth parameter mongod --auth more information here
Read more

r - Update two sets of radiobuttons reactively - shiny -

i have read ( how make choices in radiobuttons reactive in shiny? ) shows me how update radiobutton s in reactive way. however, when try , update 2 sets of buttons same data, 1 set renders. example: server: # create example data wafer <- rep(c(1:3), each=3) length <- c(1,1,2,1,1,1,3,5,1) width <- c(3,1,6,1,1,1,1,1,6) dd <- data.frame(wafer, length, width) shinyserver(function(input, output, session){ # create reactive dataframe store data values <- reactivevalues() values$df <- data.frame() # lengths , widths of wafer user input <- eventreactive(input$do, { subset(dd, wafer %in% input$wafer, select = length:width) }) # update reactive data frame lengths , widths have been selected user input observe({ if(!is.null(a())) { values$df <- rbind(isolate(values$df), a()) } }) output$wl <- renderdatatable({ a() }) # update radio buttons unique length , widths stored in values$df # ever "observe" put first in co...
Read more

ios - Realm over CoreData should I use NSFetchedResultController or a Dictionary? -

i'm working on app using core data , nsfetchedresultcontroller many reasons switch use realm. saw there "realm version" of nsfetchedresultcontroller on github wouldn't compatible current code using core data. the view controller displaying list of people same school, address book. list sublist of people studied in same city. so thinking make 1 unique request database retrieve list of people , filter locally list within 1 dictionary per school [string: anyobject] string section name within tableview , anyobject array of people. first solution, make nsfetchedresultcontroller each school predicate filtering location. delete actions etc.. handled delegates -> not compatible realm create dictionaries , update them each actions... -> works realm it's annoying code. any better solution? edit: i need clarify request: i'd write class inherit uitableviewcontroller. this class has list of people sorted in alphabetical order the tableview has ...
Read more