Bugs while deploying AI edge

[kaleygel]

When copying & pasting the hostname, it does not respect https://

Error details are ambiguous for users - if we are serving up the error code, how can we make it clearer for users with ID to help better troubleshoot & resolve. For whatever error codes we deliver, we should provide a definition (example: https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/)

GitHub needs to be capitalized" H" on error page

Design: Widow

[jacobsmith928]

@mattdjenkinson if you take a look at this, I guess the "copy" default hostname should have included the https but also the system should have forced https. It didn't do either.

[kaleygel]

As an additional bug - I'm unable to delete as well.

[mksinghtx]

@kaleygel I think the confirmation string does not match your resource there is a hyphen "testing123" is expected while in the confirmation string it is "testing-123". I was able to delete my resources

[jacobsmith928]

Yeah that looks like it - good eye @mksinghtx. Tagging in @mattdjenkinson since he is pushing a chance to the flow to make it as simple as typing DELETE.

[kaleygel]

Ahh thank you eagle eyes!! Yeah a simple "DELETE" would be better I guess!

[mattdjenkinson]

Thanks for the feedback @kaleygel - fixes incoming 🤙🤙

[mattdjenkinson]

@kaleygel regarding the copying of https, the browser will automatically try https and then fallback to http it if there's no certificate. Was there a specific issue you had when trying to reach the url?

[jacobsmith928]

@mattdjenkinson when we tried the url it brought up a 503 but not true error page. I guess the expectation was that it would force https (not fallback) because the "force https" was enabled. And then since their was no actual origin (we were just testing) it would show the error page.

when we replaced the url string with https we got the expected error page.

[mattdjenkinson]

Ah ok that makes sense, will investigate!

[zachsmith1]

here is a list of some of the potential errors we could get back from envoy. note, it won't be exhaustive. https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/response_code_details

[kaleygel]

Those descriptions IMO are super helpful - way more helpful than just the "name" detail as a user