HTTP client error 401, 404, 502: Difference between revisions
(New page: adfgadfgadfg) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
==Applies To== | |||
All devices using HTTP as client (PBX's with external MOH. Waiting queues with announcement. Devices with UPDATE client. Phone trying to load background image. etc.) | |||
==More Information== | |||
HTTP transaction fails with some HTTP error code, e.g. <code>502</code>: | |||
63:3043:519:3 - HTTPCLIENT WEBMEDIA-CH.4: GET https://10.20.30.40/DRIVE/CF0/MOH/music_on_hold.g711a | |||
63:3043:543:7 - WEBMEDIA-CH.0: http error: 502 | |||
To see HTTP client error messages, you may want to enable the HTTP client trace (''HTTP Client'' in ''Maintenance/Diagnostics/Tracing'' or even better ''Client'' and ''verbose'' in the ''HTTP'' section of the debug page (http://x.x.x.x/debug.xml)). | |||
===Meaning=== | |||
Transport error (cannot connect to server). | |||
The HTTP error response status is defined by the HTTP protocol. Common error message include: | |||
* 401. The client has no sufficient access right to access the URL on the HTTP server | |||
* 404. The resource pointed to by the URL does not exist. You probably misspelled the path or name | |||
* 502. Might indicate problems with a proxy server on the far end | |||
: However, the HTTP client currently generates 502 for all errors which occur outside from HTTP, such as badly formed URLs (e.g. <code>http:172.31.2.3/drive/cf0/update/update-all.txt</code>), un-resolved DNS names or bad certificates in case of HTTPS. | |||
More about HTTP error codes can be found in the [http://de.wikipedia.org/wiki/HTTP-Statuscode German] and [http://en.wikipedia.org/wiki/List_of_HTTP_status_codes English] wikipedia. | |||
===Solution=== | |||
Validate IP address, DNS names (if used) and access rights and check certificate configuration (looking at ''General/Certificates'' on the requesting box). | |||
<!--*[[Main_Page|wiki-innovaphone]]--> | |||
[[Category:Faq|{{PAGENAME}}]] | |||
Latest revision as of 08:42, 5 April 2013
Applies To
All devices using HTTP as client (PBX's with external MOH. Waiting queues with announcement. Devices with UPDATE client. Phone trying to load background image. etc.)
More Information
HTTP transaction fails with some HTTP error code, e.g. 502:
63:3043:519:3 - HTTPCLIENT WEBMEDIA-CH.4: GET https://10.20.30.40/DRIVE/CF0/MOH/music_on_hold.g711a 63:3043:543:7 - WEBMEDIA-CH.0: http error: 502
To see HTTP client error messages, you may want to enable the HTTP client trace (HTTP Client in Maintenance/Diagnostics/Tracing or even better Client and verbose in the HTTP section of the debug page (http://x.x.x.x/debug.xml)).
Meaning
Transport error (cannot connect to server).
The HTTP error response status is defined by the HTTP protocol. Common error message include:
- 401. The client has no sufficient access right to access the URL on the HTTP server
- 404. The resource pointed to by the URL does not exist. You probably misspelled the path or name
- 502. Might indicate problems with a proxy server on the far end
- However, the HTTP client currently generates 502 for all errors which occur outside from HTTP, such as badly formed URLs (e.g.
http:172.31.2.3/drive/cf0/update/update-all.txt), un-resolved DNS names or bad certificates in case of HTTPS.
More about HTTP error codes can be found in the German and English wikipedia.
Solution
Validate IP address, DNS names (if used) and access rights and check certificate configuration (looking at General/Certificates on the requesting box).