[Bug]: unable to verify the first certificate

[Nu1i]

Describe the bug

When accessing an HTTPS website, an error is prompted，“unable to verify the first certificate”

To reproduce

1. Go to ...
   add a https request and click send button.
2. Click on send button
3. Scroll down to response area, it show me "Request failed unable to verify the first certificate"
4. See error

App Version and Architecture

To solve this problem, please add a feature to skip server certificate verification.

amd64

System info

System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
    Memory: 5.12 GB / 15.74 GB

Validations

• Follow our Code of Conduct
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.

[github-actions]

Hello @Nu1i. Please describe in detail the sequence of actions that leads to the bug (skip it if it's already there). Add screenshots of errors from the console. If possible add a video. Issues marked with need reproduction will be closed if they have no activity within 3 days.

[antonreshetov]

Thanks for the update.

This is not a confirmed bug. massCode currently uses standard HTTPS certificate verification, and this error usually means the server certificate chain is not trusted by the client.

Skipping certificate verification would be a new opt-in HTTP client feature, not a bug fix. We use issues only for confirmed bugs, so please open a GitHub Discussion for this feature request.

If you can provide a public URL with a valid certificate that works in other clients but fails in massCode, we can reopen/reconsider this as a bug

[Nu1i]

Thanks for the update.

This is not a confirmed bug. massCode currently uses standard HTTPS certificate verification, and this error usually means the server certificate chain is not trusted by the client.

Skipping certificate verification would be a new opt-in HTTP client feature, not a bug fix. We use issues only for confirmed bugs, so please open a GitHub Discussion for this feature request.

If you can provide a public URL with a valid certificate that works in other clients but fails in massCode, we can reopen/reconsider this as a bug

Most of the time, SSL certificates for testing programs are generated temporarily, rather than certificates issued by trusted certificate authorities. As you know, applying for a certificate from a trusted digital certificate authority as a site certificate for testing programs is very expensive. Therefore, most of the time we use self-signed certificates as server site certificates for testing environments. However, the current status of MassCode does not allow access to sites with self-signed certificates. Tools like Postman provide a function to skip certificate verification to avoid the issue of being unable to access sites with self-signed certificates as server site certificates. I sincerely hope this problem can be resolved.

postman setting

[antonreshetov]

That’s right, but it’s not a bug, it’s the feature you want

[Nu1i]

That’s right, but it’s not a bug, it’s the feature you want

Okay, I understand, but I have a question. When I access this link using Edge and Google Chrome, there are no errors or issues with the certificate not being trusted, but when I send a request using MassCode's HTTP client, it reports an error. The error message is 'unable to verify the first certificate'. the link is "https://svapp.isccc.gov.cn/"