liuxiran commented on issue #2013: URL: https://github.com/apache/apisix-dashboard/issues/2013#issuecomment-894761136
> After my verification, no matter what the `Admin API` is used to create this content, the `dashboard` is behaving normally. > > The only thing that needs to be done is when the dashboard creates a single `uri/host/remote_addr`, we need to set the field in the request body to `uri/host/remote_addr`. > > Currently, whether it is single or multiple, it is `uris/hosts/remote_addrs`. I'm glad to hear that Web can behave normally no matter what what is used by `Admin API`, and thanks for @Baoyuantop verification. Based on this conclusion, could we consider pushing forward the optimization of `Admin API` @juzhiyuan ? That is to say, since `APISIX` support multiple `uris/remote_addrs/hosts` in one `Route`, only `uris/remote_addrs/hosts` is enough IMO, `uri/remote_addr/host` the existence of this set of parameters only increased barriers to choice for users. What we need to do is just like current: no matter what parameters passed in `Admin API`, web can both behave normally. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
