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

RSE ignores protocol set to http, always tries https #466

Open
zFernand0 opened this issue Jan 6, 2025 · 3 comments
Open

RSE ignores protocol set to http, always tries https #466

zFernand0 opened this issue Jan 6, 2025 · 3 comments
Labels
question Further information is requested

Comments

@zFernand0
Copy link

zFernand0 commented Jan 6, 2025

Describe the bug
RSE ignores protocol set to http, always tries https.

To Reproduce
Steps to reproduce the behavior:

  1. Start RSEAPI SECURE='false'
  2. Set RSE in like (notice that protocol is set to http):
        "rse": {
            "type": "rse",
            "properties": {
                "host": "<YOUR HOST>",
                "port": 6800,
                "basePath": "rseapi",
                "protocol": "http",
                "user": "<YOUT USER>",
                "password": "<YOUR PASSWORD>"
            },
            "secure": [
                "user",
                "password"
            ]
        },

In zowe's configuration file.

  1. Any operation (dataset, uss, jobs) fails with the error message:

Retrieving response from MVS list API Error: Failed to send an HTTP request.

  1. You can see in the OUTPUT tab that https was tried instead of http:
[2025/01/05 13:50:33] [ERROR] Error: Failed to send an HTTP request.
{
  errorDetails: [i [Error]: Failed to send an HTTP request.
  	at c.populateError (c:\Users\sergi\.vscode\extensions\ibm.zopeneditor-5.1.0\dist\extension.js:2:418090)
  	at ClientRequest.<anonymous> (c:\Users\sergi\.vscode\extensions\ibm.zopeneditor-5.1.0\dist\extension.js:2:408742)
  	at ClientRequest.emit (node:events:530:35)
  	at emitErrorEvent (node:_http_client:101:11)
  	at TLSSocket.socketErrorListener (node:_http_client:504:5)
  	at TLSSocket.emit (node:events:518:28)
  	at emitErrorNT (node:internal/streams/destroy:169:8)
  	at emitErrorCloseNT (node:internal/streams/destroy:128:3)
  	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)] {
    mDetails: {
      msg: 'Failed to send an HTTP request.',
      causeErrors: [Error: write EPROTO 271360:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:..\..\third_party\boringssl\src\ssl\tls_record.cc:231:
      
      	at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:95:16)] {
        errno: -4046,
        code: 'EPROTO',
        syscall: 'write'
      },
      source: 'client',
      errorCode: undefined,
      protocol: 'https',
      port: 6800,
      host: 'XXXXX',
      basePath: 'rseapi',
      httpStatus: undefined,
      errno: undefined,
      syscall: undefined,
      payload: undefined,
      headers: [],
      resource: '/api/v1/jobs?status=*',
      request: 'GET',
      additionalDetails: 'HTTP(S) client encountered an error. Request could not be initiated to host.\n' +
        'Review connection details (host, port) and ensure correctness.\n' +
        '\n' +
        'Protocol:          https\n' +
        'Host:              XXXXX\n' +
        'Port:              6800\n' +
        'Base Path:         rseapi\n' +
        'Resource:          /api/v1/jobs?status=*\n' +
        'Request:           GET\n' +
        'Headers:           []\n' +
        'Payload:           undefined\n' +
        'Auth type:         basic\n' +
        'Allow Unauth Cert: false'
    },
    mMessage: 'Failed to send an HTTP request.'
  },
  label: 'rse_OLS0009',
  moreInfo: 'Retrieving response from JES list API'
}

Expected behavior

Be able to use the Zowe Explorer with http

Desktop (please complete the following information):

  • OS: Windows 11 23H2
  • Zowe Explorer Version: v3.0.3
  • (Optional) Zowe CLI Version:
  • (Optional) Are you using Secure Credential Store?: NO

Additional context

RSEAPI is accessible via Swagger.


Originally posted by @ssamayoa

@JillieBeanSim
Copy link
Member

JillieBeanSim commented Jan 6, 2025

This is a known issue listed in IBM Z Open Editor docs for troubleshooting linking to the existing Zowe CLI issue created when support issues for extenders with HTTP connections started which is still opened in their repository waiting solution.

@ssamayoa
Copy link

ssamayoa commented Jan 6, 2025

I wonder if is a well know issue, why hasn't be resolved?

What about raise an error with "http is NOT SUPPORTED only https"?

If I got such message I wouldn't wasted time creating the bug report and others reading and acting on it.

@JillieBeanSim
Copy link
Member

JillieBeanSim commented Jan 6, 2025

Thanks @ssamayoa for the feedback, will reopen for discussion of update to value descriptions and possible checks with explanations until support can be restored for http.

@JillieBeanSim JillieBeanSim reopened this Jan 6, 2025
@phaumer phaumer added the question Further information is requested label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants