Adding failing spec for issue 406

[seansu4you87]

• headers not respected for autogenerated OPTIONS routes

#406

[seansu4you87]

I'm not sure how to actually fix this. I took a while to poke through, and it looks like the Grape::Endpoint has a @Header variable. When a route is being run, the before blocks, etc in the settings (Grape::Util::HashStack) code gets run, that then populates this @Header variable.

In Grape::API#add_head_not_allowed_methods, how do I access a populated @Header of the endpoints without actually executing all of that code?

[jackbit]

i use /~https://github.com/cyu/rack-cors to handle RACK OPTIONS issue. In application.rb i added these lines:

ApplicationServer = Rack::Builder.new {
  # ...
  use Rack::Cors do
    allow do
      origins '*'
      resource '*', headers: :any, methods: [:get, :post, :put, :delete, :options]
    end
  end
  # ...
}

[dblock]

#498 fixed adding a header in a before block, but an OPTIONS doesn't hit the API, right? Do we think this test is valid?

[dblock]

@karlfreeman @seansu4you87 Can we close this?

[karlfreeman]

Yep. #498 + #582 closes this.

[dblock]

Closed.