jeffpriz / vsts-release-web-test Goto Github PK

Hi I'm getting a HPE_HEADER_OVERFLOW error with one of my urls.

I'm guessing it's because of the large CSP header for that url.

Is there a way to bypass this issue, other than removing the CSP header?
Alternatively, would sending a HEAD request help, and how do I do that?

Log is:
2022-07-28T02:44:15.4573394Z Status Code is:{"name":"RequestError","message":"Error: Parse Error","cause":{"bytesParsed":4096,"code":"HPE_HEADER_OVERFLOW"},"error":{"bytesParsed":4096,"code":"HPE_HEADER_OVERFLOW"},"options":{"method":"GET","uri":"myurl","simple":false,"resolveWithFullResponse":true,"strictSSL":true,"transform2xxOnly":false}}

Option to publish the outcome as a test result since this can be used in the pipeline logic or reporting.

Hello,

when i try to use a variable instead of the URL it gives me an error.

Is the URL field compatible with variables?

Why is there an arbitrary max retries limit of 12?

We have some systems that can take 1-5 mins to initialize. The 12 retries limit is way too low to account for this. Can we remove this limit or at least put a maximum that is more sensible (e.g. 100) so that we don't need to put long delays as a workaround?

Thanks

Does this smoke test have the ability to pass on basic authentication?

Can I do this:

https://{version}/myApp.com

so that I can supply different urls depending on a environment variable?

Is it possible to allow more than one return code for success?

200 or 401

It would be really useful to add the possibility to get URLs using an HTTP proxy. There are some on-premise landscapes or companies where the direct Internet-Access is not allowed and the extension fails while trying to reach them.

I've tried to use it with an agent configured behind a proxy and the issue still happening.

We're deploying our feature branches to an Azure App Service. I'd like to be able to smoke test them after they are up, but to be able to hit the URL I have to sign in with an Azure AD account. It would be great if there was a way to support this.

This warning appears every time the Web Smoke Test release task runs.

(node:7624) Warning: Use Cipheriv for counter mode of aes-256-ctr

I see the extension is almost 8.5Mb. It seems very big for what it does. Do you really need all node_modules to make it work? I'm not a node guru though...

When we update an application, a new version value is set and the smoke or health endpoint returns this value, so if we are in a k8s environment, the response could be answered by an old pod that has the old version, so if your extension can validate not only the http status but also the response value (ex: from JSON) it could be great!

Is there any way to deploy last successful release when the smoke test is failed