#6 closed defect (fixed)
WMS Identify fails to provide a useful error message on failure
| Reported by: | morb_au | Owned by: | morb_au |
|---|---|---|---|
| Priority: | minor: annoyance | Milestone: | |
| Component: | WMS | Version: | Trunk |
| Keywords: | ogc ows wms GetFeatureInfo proxy | Cc: | |
| Must Fix for Release: | No | Platform: | All |
| Platform Version: | Awaiting user input: | no |
Description
If the Identify tool is used on a WMS layer but the request fails, the returned error message shows nothing useful.
It's probably a simple problem with the error messages not being passed back properly from QgsHttpConnection and QgsWmsProvider.
Change History (5)
comment:1 by , 18 years ago
| Status: | new → assigned |
|---|
comment:2 by , 18 years ago
| Keywords: | proxy added |
|---|
comment:3 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
I saw a useful error message come back in the HEAD build yesterday, which prompted my lodging of enhancement request #196.
Therefore I must have lodged a fix to this without noticing (!). Closing accordingly.
comment:4 by , 17 years ago
| Awaiting user input: | unset |
|---|---|
| Must Fix for Release: | → No |
Note:
See TracTickets
for help on using tickets.
Hi,
the same happens here, when using a proxy:
"Could not understand the response. The wms provider said: " (nothing).
SVN checkout date 3 July 2006, full compilation, Proxy used, RHEL4 Linux
Greetings, Markus