Skip to content

Server Object host field compatibility with protocols #1016

Open
@smoya

Description

Recently we got a question in our Slack regarding a particularity on ibmqp binding. The question lead to checking that specifying a CCDT connection file should be possible in v3:

asyncapi: 3.0.0
info:
  title: Test
  version: 0.1.0
servers:
  production1:
    host: 'http://my-ccdt-json-file/'
    protocol: ibmmq
  production2:
    host: 'file://myccdt.json/'
    protocol: ibmmq

As you can see, the host includes the protocol converting it to a URL, something I understand not expected in v3 or even somehow illegal. The URL in rendered docs look like ibmmq://http://my-ccdt-json-file/ and ibmmq://file://myccdt.json/ respectively.

The question is, should a URL be allowed as a value for the host field? The spec doesn't mention anything about. Not even a "the host field should not be a URL".

Whatever direction we take, we should clarify what the host is expected or not to include.

Slack thread: https://asyncapi.slack.com/archives/C0230UAM6R3/p1706705627052239

Metadata

Assignees

No one assigned

    Labels

    stale❔ QuestionA question about the spec or processes

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions