{"action":"opened","issue":{"url":"https://api.github.com/repos/novnc/noVNC/issues/1096","repository_url":"https://api.github.com/repos/novnc/noVNC","labels_url":"https://api.github.com/repos/novnc/noVNC/issues/1096/labels{/name}","comments_url":"https://api.github.com/repos/novnc/noVNC/issues/1096/comments","events_url":"https://api.github.com/repos/novnc/noVNC/issues/1096/events","html_url":"https://github.com/novnc/noVNC/issues/1096","id":336724957,"node_id":"MDU6SXNzdWUzMzY3MjQ5NTc=","number":1096,"title":"Handling HTTP 403 errors","user":{"login":"santosh0705","id":1947598,"node_id":"MDQ6VXNlcjE5NDc1OTg=","avatar_url":"https://avatars2.githubusercontent.com/u/1947598?v=4","gravatar_id":"","url":"https://api.github.com/users/santosh0705","html_url":"https://github.com/santosh0705","followers_url":"https://api.github.com/users/santosh0705/followers","following_url":"https://api.github.com/users/santosh0705/following{/other_user}","gists_url":"https://api.github.com/users/santosh0705/gists{/gist_id}","starred_url":"https://api.github.com/users/santosh0705/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/santosh0705/subscriptions","organizations_url":"https://api.github.com/users/santosh0705/orgs","repos_url":"https://api.github.com/users/santosh0705/repos","events_url":"https://api.github.com/users/santosh0705/events{/privacy}","received_events_url":"https://api.github.com/users/santosh0705/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-28T18:09:56Z","updated_at":"2018-06-28T18:09:56Z","closed_at":null,"author_association":"NONE","body":"**Is your feature request related to a problem? Please describe.**\r\nMy websockify is running in a restricted environment. It throw HTTP 403 for unauthorised access and allow connection to all authorised accesses. When noVNC fails to connect the host with a 403 error it is showing \"Failed to connect to server\" message which is not specifying the reason.\r\n\r\n**Describe the solution you'd like**\r\nWhen noVNC fails to connect the host with a 403 error it should show \"Access forbidden\" message than the message showing now.\r\n\r\n**Describe alternatives you've considered**\r\nAlternatively we can show the actual HTTP error message.\r\n\r\n**Additional context**\r\nFor testing I'm using Websockify module port for Nginx and below is my Nginx configuration configuration:\r\n\r\n```\r\n    location = /auth {\r\n        internal;\r\n        return    403;\r\n    }\r\n\r\n    location /vncterm/ {\r\n        auth_request            /auth;\r\n\r\n        websockify_pass         172.16.64.130:5900;\r\n        websockify_read_timeout 120s;\r\n        websockify_send_timeout 120s;\r\n    }\r\n```\r\n\r\nFor testing I'm returning 200 or 403 manually on /auth location."}}
{"actor":{"display_login":"santosh0705"}}