Manu Garg

I've been thinking of adding this as well. I was looking at selenium and playwright for this kind of testing. Both of them provide rich browser testing - open the...

Update: I've given it more thought and have been working on a possible solution using [cypress](https://www.cypress.io/). As UI testing tends to be pretty heavy and there may be cases where...

Another possibility is to create an alternate docker image and set up cypress in that image. We can then simply use that cypress instance. It will probably simplify things.

As per the article here https://www.checklyhq.com/blog/cypress-vs-selenium-vs-playwright-vs-puppeteer-speed-comparison/, playwright might be a better choice for this, mainly because of its better startup time. In fact, checkly provides browser based synthetic monitoring using...

@matt-malarkey Thank you for reporting the issue and researching it. Off the top of my head, this sounds reasonable to me. I'll think more about it.

Sorry for dropping the ball on this one, but I was looking at it again (yes, I know after a year :() and realized that connect headers will likely look...

#763 adds proxy_connect_headers field.

I think tracking individual use case like this is not going to work well. I'm trying to think of some generic approach to validators.

Adding a new metric is expensive in the sense that it affects everyone automatically, so we don't do that unless it's something that applies to a lot of use cases,...

I am going to merge this into #356.