-
Notifications
You must be signed in to change notification settings - Fork 93
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
URL issue #206
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a url for my rest api that is structured like this:
https://[fqdn]/[servicename]/Service2.svc/[interfacegroup]/[interface]/?operation=MonitorID¶mater=5
The issue is that when I setup swaggerui it does not see the [servicename] and brings up the addresses like this in the request url section
https://[fqdn]/Service2.svc/[interfacegroup]/[interface]/?operation=MonitorID¶mater=5
We have found a work around using IIS but just wanted to report this. Also I have found that something similar happens with the [interfacegroup] I get 2 interface instances for each interface.
one like this:
https://[fqdn]/Service2.svc/[interface]/?operation=MonitorID¶mater=5
and one like this
https://[fqdn]/Service2.svc/[interfacegroup]/[interface]/?operation=MonitorID¶mater=5
If I specify the [interfacegroup] with swaggerwcppath.
Thank you.
The text was updated successfully, but these errors were encountered: