feat: about the stream routes button error report page in new dashboard

[bakerLecter]

Description

The new dashboard will crash if stream routes isn't enable when you click the stream routes button. This make sense but there is no button for user return back to the dashboard from the error report page.

Stream routes isn't something using everywhere for every cluster. I think it could reduce the wrong operation if stream routes button will hidden when the stream routes function isn't enable. Or at least this error will not redirect user to a split error page, just show up as a notify right side of the page.

[Baoyuantop]

This make sense but there is no button for user return back to the dashboard from the error report page.

I usually just click the browser's back button.

I think it could reduce the wrong operation if stream routes button will hidden when the stream routes function isn't enable.

This effect is acceptable, but I'm not sure if the current API can support implementing it. cc @SkyeYoung

[SkyeYoung]

In fact, this page looks like this when using the e2e server.

This also has e2e test: https://github.com/apache/apisix-dashboard/blob/master/e2e/tests/stream_routes.show-disabled-error.spec.ts#L99

It seems that there are some problems with apisix configuration.

[SkyeYoung]

Please retransfer this issue to apisix.

[bakerLecter]

This is how I config the apisix setting，if I remove proxy_mode and stream_proxy could reproduce this problem.

    apisix:
      extra_lua_path: "/usr/local/apisix/custom-plugins/?.lua"
      control:
        ip: "0.0.0.0"
        port: 9092
      enable_control: true
      data_encryption:
        enable_encrypt_fields: false
        keyring:
          - some_string
          - some_string
      enable_ipv6: false
      enable_http2: true
      enable_server_tokens: false
      router:
        http: radixtree_host_uri
      proxy_mode: http&stream
      stream_proxy:
        tcp:
          - 3001
          - 3003
          - 3007
          - 3012
          - 3013
          - 3014
          - 3015
          - 9100
          - 8873
        udp:
          - 9200
      node_listen:
        - port: 80
        - port: 9080
      ssl:
        enable: true
        fallback_sni: "*.some.legal.domain.com"
        listen:
          - port: 443
        ssl_ciphers: "ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-CHACHA20-POLY1305:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA256:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA"
        #ssl_ciphers: "ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA256:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA"
        ssl_protocols: "TLSv1 TLSv1.1 TLSv1.2"
        ssl_session_tickets: false

[bakerLecter]

This is the request detail.

And I find my api-key show up in the request header, it this safe?

this is the response for this request: {error_msg: "stream mode is disabled, can not add stream routes"}

[Baoyuantop]

1. The left menu should always be displayed.
2. Optimization tips, explaining why the current error occurred and where to enable this configuration.

[SkyeYoung]

@bakerLecter

And I find my api-key show up in the request header, it this safe?

Why do you think it's not safe?

When you use curl to directly request the admin API, does it not show the header?

[SkyeYoung]

This should be fixed in bee39c2. But it's not included in the released apisix.