[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDV #BSD-546165]: Accessing non OpenDAP urls

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [IDV #BSD-546165]: Accessing non OpenDAP urls
  • Date: Sat, 16 Dec 2006 00:03:59 -0700
Hi all,

> 1. All errors on my servers are redirected to a script that processes
> errors (I get emails for some of them), so errors will report back
> as 302 rather than 404.

This seems like a dangerous precedent as it gives the client no indication that 
their request has failed. Actually, the redirect with the 302 isn't the 
problem. It is the 200 response code for the resulting page that causes the 
client to think it has succeeded.

Have you thought about giving that final page a 404 response code rather than a 
200? That would provide clients with a a more accurate representation of what 
is happening on the server.

That accurate picture is what allows automated clients to function on the web.

Thanks,

Ethan

Ticket Details
===================
Ticket ID: BSD-546165
Department: Support netCDF Java
Priority: Normal
Status: Closed