Skip to content

Consider not requiring HTTPS for custom meta schemas #314

@dnedev

Description

@dnedev

Hello,

Since release 1.0.40 custom meta schemas must be accessed over HTTPS. Unfortunately, some 3rd party schemas we use come from hosts that do not support HTTPS. As a result, we experienced a lot of schema validation issues and had to downgrade.

  • Is it possible to disable the requirement that all custom schemas must be retrieved over HTTPS?
    • If not, would you consider adding an option for that?

Thanks!

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