Skip to content

404 returned when a more specific code should be returned #60

@jbfaden

Description

@jbfaden

I don't think a 404 is the correct response when the dataset does not exist:

spot9> wget -O - 'https://cottagesystems.com/server/cdaweb/hapi/data?id=AC_H2_SIS/availability&parameters=&time.min=2024-01-01T00:00Z&time.max=2025-09-01Z'
--2025-03-17 17:34:52--  https://cottagesystems.com/server/cdaweb/hapi/data?id=AC_H2_SIS/availability&parameters=&time.min=2024-01-01T00:00Z&time.max=2025-09-01Z
Resolving cottagesystems.com (cottagesystems.com)... 199.188.64.196
Connecting to cottagesystems.com (cottagesystems.com)|199.188.64.196|:443... connected.
HTTP request sent, awaiting response... 404 
2025-03-17 17:34:53 ERROR 404: (no description).

(should be

wget -O - 'https://cottagesystems.com/server/cdaweb/hapi/data?id=AC_H2_SIS/source&parameters=&time.min=2024-01-01T00:00Z&time.max=2025-09-01Z'

)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions