Skip to content

Construct URLs based on service capabilities #1317

@delucchi-cmu

Description

@delucchi-cmu

Feature request

If a service doesn't support additional HTTP parameters, we shouldn't put them on our request URLs.

This arose this week out of constraints on the filter HTTP parameters allowed in CDS HATS-on-the-fly catalogs.

However, once we have access to the full VO Resource from the registry (see astronomy-commons/hats#654), we can know which HTTP parameters are supported and allow pass those through.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions