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

ZnHTTPSTests>>testAmazonAWS has been randomly failing, but the last 4 montly runs have failed, so it is time to look for solutions #107

Closed
dalehenrich opened this issue Aug 13, 2024 · 3 comments
Assignees

Comments

@dalehenrich
Copy link
Member

@kurtkilpela has suggested the following would work:

exec
| caCert socket |
caCert := GsSecureSocket setCaCertLocation.
GsFile gciLogClient: caCert.
socket := GsSecureSocket newClient.
socket
  connectTo: 443
  on: 'aws.amazon.com'
  timeoutMs: 50.
"socket setServerNameIndication: 'aws.amazon.com'."
socket secureConnect.
socket
%

however, the test framework is a bit more complicated and does not expose the socket so nicely ... so this is a job for @kurtkilpela, himself ...

@kurtkilpela
Copy link

To clarify a bit, the code in Dale's posting exhibits a similar (perhaps the same) failure as the test case. Inspecting the underlying GsSecureSocket during a failure, it does not appear to set the SNI when ZnClient is used in GemStone.

This information was used to mimic the behavior with a GsSecureSocket.

@kurtkilpela
Copy link

I have been able to confirm that if I set an SNI when using ZnClient, `https://aws.amazon.com' will load without error.

@kurtkilpela
Copy link

Resolved by PR #108

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants