{"action":"created","issue":{"url":"https://api.github.com/repos/domaindrivendev/Swashbuckle/issues/193","labels_url":"https://api.github.com/repos/domaindrivendev/Swashbuckle/issues/193/labels{/name}","comments_url":"https://api.github.com/repos/domaindrivendev/Swashbuckle/issues/193/comments","events_url":"https://api.github.com/repos/domaindrivendev/Swashbuckle/issues/193/events","html_url":"https://github.com/domaindrivendev/Swashbuckle/issues/193","id":57971188,"number":193,"title":"{\"message\":\"Internal server error\"}","user":{"login":"DotNetRockStar","id":9408944,"avatar_url":"https://avatars.githubusercontent.com/u/9408944?v=3","gravatar_id":"","url":"https://api.github.com/users/DotNetRockStar","html_url":"https://github.com/DotNetRockStar","followers_url":"https://api.github.com/users/DotNetRockStar/followers","following_url":"https://api.github.com/users/DotNetRockStar/following{/other_user}","gists_url":"https://api.github.com/users/DotNetRockStar/gists{/gist_id}","starred_url":"https://api.github.com/users/DotNetRockStar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DotNetRockStar/subscriptions","organizations_url":"https://api.github.com/users/DotNetRockStar/orgs","repos_url":"https://api.github.com/users/DotNetRockStar/repos","events_url":"https://api.github.com/users/DotNetRockStar/events{/privacy}","received_events_url":"https://api.github.com/users/DotNetRockStar/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-02-17T19:40:06Z","updated_at":"2015-02-20T17:59:44Z","closed_at":"2015-02-20T17:59:44Z","body":"I pulled the nuget package down (Swashbuckle) on a brand new sample application and ran the project with no problems.  /swagger/docs/v1 worked perfectly.\r\nI pulled the nuget package down (Swashbuckle) on a large existing application I have (same version of Web Api and Swashbuckle) and I get this when I do a GET /swagger/docs/v1\r\n\r\n{\"message\":\"Internal server error\"}\r\n\r\n:*(\r\nHow might I troubleshoot something like this?"},"comment":{"url":"https://api.github.com/repos/domaindrivendev/Swashbuckle/issues/comments/75288021","html_url":"https://github.com/domaindrivendev/Swashbuckle/issues/193#issuecomment-75288021","issue_url":"https://api.github.com/repos/domaindrivendev/Swashbuckle/issues/193","id":75288021,"user":{"login":"domaindrivendev","id":1434343,"avatar_url":"https://avatars.githubusercontent.com/u/1434343?v=3","gravatar_id":"","url":"https://api.github.com/users/domaindrivendev","html_url":"https://github.com/domaindrivendev","followers_url":"https://api.github.com/users/domaindrivendev/followers","following_url":"https://api.github.com/users/domaindrivendev/following{/other_user}","gists_url":"https://api.github.com/users/domaindrivendev/gists{/gist_id}","starred_url":"https://api.github.com/users/domaindrivendev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/domaindrivendev/subscriptions","organizations_url":"https://api.github.com/users/domaindrivendev/orgs","repos_url":"https://api.github.com/users/domaindrivendev/repos","events_url":"https://api.github.com/users/domaindrivendev/events{/privacy}","received_events_url":"https://api.github.com/users/domaindrivendev/received_events","type":"User","site_admin":false},"created_at":"2015-02-20T17:59:44Z","updated_at":"2015-02-20T17:59:44Z","body":"See issue #142 for a full discussion\r\n\r\nBottom line is that the Swagger 2.0 spec does not allow URI's that differ only in query component to be described as separate operations.\r\n\r\nAs Swagger is just a HTTP/REST description language and is agnostic of implementation, there is nothing stopping you from routing to different actions based off query string only but you just can't describe them as separate actions. If you don't want to change your impl, SB provides a kind of \"merge\" option to combine conflicting actions into one Operation description. See here for details https://github.com/domaindrivendev/Swashbuckle#working-around-swagger-20-constraints\r\n\r\n"}}