Chrome javascript error: Refused to get unsafe header "X-MiniProfiler-Ids" about rack-mini-profiler HOT 12 CLOSED

Yes we are aware of this @OsamaSayegh is investigating a fix here.

from rack-mini-profiler.

I added this - headers['Access-Control-Expose-Headers'] = 'X-MiniProfiler-Ids', still does not seem to work at all.

from rack-mini-profiler.

Add this header to response "Access-Control-Expose-Headers"

Response.AddHeader("Access-Control-Expose-Headers", "X-MiniProfiler-Ids");

from rack-mini-profiler.

I'm seeing this anyone else?

from rack-mini-profiler.

I started seeing this when using angular with cross origin resources and CORS. See for example http://jaketrent.com/post/expose-http-headers-in-cors/

from rack-mini-profiler.

Yeah. Any solution for this?

from rack-mini-profiler.

This looks like it will need to tie into cors of the main app.
Or at least provide partial cors support for at least own responses

from rack-mini-profiler.

@steverob What gem are you using that introduced cors?
I wonder if we can detect this gem and add a rule for this page

from rack-mini-profiler.

I'm using rack-cors and the following line did not work:

    headers["Access-Control-Expose-Headers"] = "X-MiniProfiler-Ids"

from rack-mini-profiler.

For me, this error seems to stem from using Invoker. Not entirely sure how Invoker operates, but it's like it's proxying <domain>.<tld> to localhost:<port>. If I access my app's dev server through localhost: there is no error, which makes sense. There's something Invoker must be doing or not doing differently compared to e.g. puma-dev or pow.

Can't speak for everyone's situation though.

from rack-mini-profiler.

Don't like the +1's but Seeing the same error.

from rack-mini-profiler.

This was fixed in d62736e.

from rack-mini-profiler.