[
https://issues.apache.org/jira/browse/CXF-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984460#comment-15984460
]
Peter van den Broek commented on CXF-7347:
------------------------------------------
Sergey,
I've attached 2 screenshots, one that shows the Swagger UI basepath when going
to 127.0.0.1 and one for localhost.
When visiting 127.0.01, the basepath is still resolved to "localhost".
This isn't the case in the previous version.
!swagger-ui-basepath-127001.PNG!
!swagger-ui-basepath-localhost.PNG!
> Support Swagger UI 3
> --------------------
>
> Key: CXF-7347
> URL: https://issues.apache.org/jira/browse/CXF-7347
> Project: CXF
> Issue Type: New Feature
> Reporter: Peter van den Broek
> Assignee: Sergey Beryozkin
> Attachments: swagger3.png, swagger-ui-basepath-127001.PNG,
> swagger-ui-basepath-localhost.PNG
>
>
> Swagger UI 3.0.0 was released on 18 March 2017 and brings a full rewrite of
> the UI from the ground up.
> In this version, they've changed the directory structure to being flat with
> only a couple of files left.
> This means the CSS and JS files are now located in the root of the folder and
> most files have been merged or removed.
> Swagger2Feature contains an internal SwaggerUIResourceFilter that checks for
> files in these (no longer existing) subfolders, but does not find the new
> location of (for example) css files.
> The pattern it uses is:
> {code}
> .*[.]js|/css/.*|/images/.*|/lib/.*|.*ico|/fonts/.*
> {code}
> This no longer works, since it doesn't allow for files (other than JS and
> ICO) to be in the root folder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
