You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jens Deppe (JIRA)" <ji...@apache.org> on 2016/06/10 16:35:20 UTC

[jira] [Updated] (GEODE-1520) Swagger UI can appear broken depending on the URL used

     [ https://issues.apache.org/jira/browse/GEODE-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jens Deppe updated GEODE-1520:
------------------------------
    Labels: bug-hunt  (was: )

> Swagger UI can appear broken depending on the URL used
> ------------------------------------------------------
>
>                 Key: GEODE-1520
>                 URL: https://issues.apache.org/jira/browse/GEODE-1520
>             Project: Geode
>          Issue Type: Improvement
>          Components: docs, rest (dev)
>            Reporter: Jens Deppe
>              Labels: bug-hunt
>
> I'm playing with the Swagger UI and followed the docs here: http://gemfire.docs.pivotal.io/docs-gemfire/latest/rest_apps/using_swagger.html
> Specifically I set {{--J=-Dgemfire.http-service-bind-address=localhost}}.
> However, browsing to http://127.0.0.1:8080/gemfire-api/docs/index.html shows me a minor error on the page {{Unable to read api 'region' from path http://localhost:8080/gemfire-api/api-docs/gemfireApi/region (server returned undefined)}} and I cannot interact with it.
> Looking at the browser console I see this error: {{No 'Access-Control-Allow-Origin' header is present on the requested resource.}}. It turns out you *MUST* use the same, literal value in the URL that you used for bind address. If you used an IP then your URL must also use an IP.
> This should be documented and/or fixed if possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)