-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Make rokwire api doc not going to 8080 #97
Comments
@sandeep-ps will review milestone assignment |
Our MVP commitment was to have App Config complete by EO July. Pulling this task back in Sprint 10 |
Based on our discussion, moving this task to sprint 11 as it is not related to App Config. |
This looks like a known bug in Swagger. |
Yes, I am aware of those two, Does Brown Dog use Swagger UI docker image? |
No, I just confirmed. We are running Swagger UI as static web app and giving the JSON file to render. For Sprint 11 (2nd Group), one temporary solution could be to run rokwire.yaml using Docker without BASE_URL and do the redirection in AWS. As this is a bug in Swagger with an open pull request (swagger-api/swagger-ui#5409), unless they merge that pull request we cannot probably use BASE_URL without running into this issue. |
Using just mapping does not work. Have to wait until the Swagger container to make the fix. |
Not yet finished; @sandeep-ps will complete or assign another dev (XX OOO next 2 weeks) |
This is happening evening with Swagger container #188. I don't think it's important to look into this at this time. Things are work fine with trailing slash in the URL. Closing this now. Will reopen if we find a solution in the future. |
Description
Currently if clicking on https://api.rokwire.illinois.edu/api/docs, my browser (Chrome) would redirect to http://...:8080/api/docs which is undesirable.
It seems there is some configuration in swagger docker that needs to be addressed.
Workaround
Use https://api.rokwire.illinois.edu/api/docs/ with / at the end.
Acceptance Criteria
not redirect to 8080
The text was updated successfully, but these errors were encountered: