Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSL Labs Test task failed in Azure pipeline #5

Open
jsnelcer opened this issue Mar 4, 2020 · 3 comments
Open

SSL Labs Test task failed in Azure pipeline #5

jsnelcer opened this issue Mar 4, 2020 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@jsnelcer
Copy link

jsnelcer commented Mar 4, 2020

Hello,

we are using SSL Labs Test task in our Azure pipeline and in 1/3 of cases this task failed with error message: "service is overloaded".
Is there any approach to avoid this?

Thank you in advance.

@kasunkv
Copy link
Owner

kasunkv commented Mar 4, 2020

Hi @jsnelcer
The "Service is overloaded" is a 529 status code that Qualys SSL Labs API returns when their API is overloaded with requests. This is not an issue from the Azure Pipelines tasks end. As of now the task is not explicitly handle the 529 status code since the task can not make an assessment about the state of the SSL Cert. So this is expected behavior. If you have any suggested improvement to handle the situation better please let me know.

SSL Labs API Error Response Status Codes

@ulieckstein
Copy link

the ssl labs api documentation states, that in case of a 529 response, you should wait for some time and then retry the call. i do understand, that when someone uses this test within a CI pipeline, blocking the pipeline for several minutes be unwanted behaviour. in our case although, we use it inside a nightly run, where waiting for 10 or even 30 minutes does not matter and would be appreciated for having a successful run. maybe this might be implemented as an optional feature.

@kasunkv
Copy link
Owner

kasunkv commented Apr 7, 2020

@ulieckstein That is a good suggestion. I will include it in the next release of the extension. Thank you.

@kasunkv kasunkv self-assigned this Apr 7, 2020
@kasunkv kasunkv added the enhancement New feature or request label Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants