Skip to content

Use NGINX terms for Client type selection #47

Closed
@ciroque

Description

@ciroque

Is your feature request related to a problem? Please describe

No problem.

To be consistent with the naming the NGINX naming should be used to not confuse users. Instead of "tcp" and "http", use "stream" and "http".

Describe the solution you'd like

I think I just did.

Describe alternatives you've considered

The current naming, which may cause confusion.

Additional context

I got nothing.

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