localhost is not allowed to access

[gcomesana]

Hi there
yes, I've read the 'Usage' section of the readme and checking the previous issues, and I have a quite opposite issue than Issue #19.
I have the API built using Rails 3 and the swagger-ui, both in the same machine, API responding on port 3003 (by running rails -p 3003 app-api), swagger-ui in the localhost/~user/Sites and, in addtition, in another_computer/~user/public_html, for remote testing purposes. In both cases, the API funcitons are listed ok, but it is impossible to make requests, I always get in debugger the (in)famous

submitting http://localhost:3003/api/uniprot/status.json
XMLHttpRequest cannot load http://localhost:3003/api/uniprot/status.json. Origin http://localhost is not allowed by Access-Control-Allow-Origin.

I have at the top of the file defining the API:

before do
    header['Access-Control-Allow-Origin'] = '*'
    header['Access-Control-Request-Method'] = '*'
    header['Access-Control-Allow-Methods'] = 'POST, GET, OPTIONS, PUT, PATCH, DELETE'
    header['Access-Control-Allow-Headers'] = 'true'
end

It is more than it is indicated at the docs, but after reading a couple of forum I just wanted to be sure.
And it is working OK if I use the online swagger-ui service...

I know I am missing something but I can't figure out what. can anybody light me up to solve this (annoying) issue??

Cheers and sorry if this is an silly (and repeating) issue.

w i l l y

[tim-vandecasteele]

Hi

Some (if not all) browsers have different/specific access rules for files loaded via file://
Try to put swagger-ui on a local webserver (put it in the rails public folder, or a quick rack app) and surf to it with the url iso file://.

Let me know if it works.

[gcomesana]

Mmmm, maybe I didn't describe the issue correctly, sorry about that.

Actually, I have the swagger-ui inside the local web server (or, in the case of the remote machine, inside its local web server). So, I can reach swagger-ui through http://localhost/~myuser/swagger-ui (or replacing localhost with my_remote_computer). Not using file:// at all, in fact I try to avoid it always I can as I know the result can be very different.

Dunno. I've just tried the same with a express application (for testing and future migration purposes) and I have the same problem, can see the API listing but no request can be done. If you have any idea, it will be fine.

Thanx again

w i l l y

[gcomesana]

Anyway, in the end it worked for me by applying the solution found @ http://stackoverflow.com/questions/13990021/swagger-ui-only-sending-options-not-post-http-method-despite-working-api, adding the middelware and, explicitely setting the base path in config/initializers/swagger.rb.

Hope the solution works for others

Cheers!!

w i l l y