Rack apps mounted in different subdomains

[Lukas Alexandre]

I'm building a Grape API alongside Sinatra. So far I've been mounting them in separate routes like this:

run Rack::URLMap.new("/" => Frontend::Server.new,
                     "/api" => API::Server.new)

Where the "/api" is served by a Grape app and "/" by a Sinatra app. But I wanted to use subdomains to separate those concerns instead of the actual "sub-URL". Any clues on how to do this?

Thanks in advance for the help.

[Daniel Doubrovkine]

I think this SO answers your question: http://stackoverflow.com/questions/19582880/rack-apps-mounted-in-different-subdomains

You don't need an URL map, use a middleware to split the two.

--
You received this message because you are subscribed to the Google Groups "Grape Framework Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ruby-grape+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

dB. | Moscow - Geneva - Seattle - New York
code.dblock.org - @dblockdotorg - artsy.net - github/dblock

[Lukas Alexandre]

Thanks!!

Lukas Alexandre

Co-Founder & Developer

CodeLogic.Me

+1 (774) 810-0163

You received this message because you are subscribed to a topic in the Google Groups "Grape Framework Discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ruby-grape/SIIDKJiIYDg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ruby-grape+...@googlegroups.com.

[Lukas Alexandre]

BTW, something just came up. Any AJAX request from the “/“ view to “API” would be considered CORS right? If so is there any know way to get around it?

Lukas Alexandre

Co-Founder & Developer

CodeLogic.Me

+1 (774) 810-0163

[Daniel Doubrovkine]

You mean circumvent CORS? It's implemented in the browser, you cannot work around that :)

[Rob Hunter]

Just to clarify some terms here - it sounds like you might be talking past each other on the CORS front.

When a page "http://example.com/" tries to access a resource "http://subdomain.example.com/", the browser considers that a violation of the famous Same Origin policy.

CORS (Cross-Origin Resource Sharing) is a way around the Same Origin Policy in that it allows servers to allow specific exemptions to the Same Origin Policy.

Grape itself doesn't enable CORS itself, but it's easy to enable CORS with a middleware gem - see the CORS section in Grape's README:
https://github.com/intridea/grape/blob/master/README.md#cors

General information on using CORS to work around the Same Origin Policy:
http://enable-cors.org/

[Daniel Doubrovkine]

Lukas, let us know if that answers your questions. 

cheers

dB.

[Lukas Alexandre]

Hi guys,

Everything did worked. But I still had the problem that serving the API from “api.” and some pages from “www.” that needed data from the API would cause CORS. That is something that I’m trying to avoid.

I really appreciate your help on this. Thanks!

Lukas Alexandre

Co-Founder & Developer

CodeLogic.Me

+1 (774) 810-0163

[Tiago Ferreira]

Hey Lukas,

I already used rack-cors with grape and goliath and everything works fine (see example below):

use Rack::Cors do
    allow do
      origins '*'
      resource '*', :headers => :any, :methods => [:get, :post,
                                                   :options, :delete]
    end

    allow do
      origins '*'
      resource '/public/*', :headers => :any, :methods => :get
    end
end

In your case, I think that you should be more restrictive about the origins. BTW, did you use rack-cors and still didn't work?

Tiago Ferreira Lima

GitHub: fltiago

Skype: fltiago

LinkedIn: linkedin.com/in/fltiago

• 
  

[Lukas Alexandre]

Hi Tiago,

Using RackCORS did worked as expected. I just don’t feel too comfortable with that approach (god knows why…). But I’ll probably have to stick with it.

Thanks!

Lukas Alexandre

Co-Founder & Developer

CodeLogic.Me

+1 (774) 810-0163