splunk / splunk/splunk-sdk-python

Search Result Export with SSL off doesn't work

Ouverte
#828 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Langage dominant
Python
Étoiles
743
Forks
387
Merge moyen
42 min
PR mergées (30 j)
4

Description

Describe the bug
When the [sslConfig] enableSplunkdSSL is set to false in server.conf, then export of search results fails, giving the following on-screen error:

Service Unavailable

This was working in the 9.* version, but has been broken in the 10.* version.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'server.conf' and set the [sslConfig] enableSplunkdSSL flag to false. Restart splunk server.
  2. Perform a search in the web search.
  3. Attempt to export the results using the down arrow.
  4. See error

Expected behavior
Results are exported

Logs or Screenshots
This log can be seen in web_service.log:

2026-08-18 06:50:23,399 ERROR	[6a8400af56192cc745880] __init__:874 - SSL error communicating with splunkd, error="[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1046)", path=/servicesNS/admin/search/search/v2/jobs/export
2026-08-18 06:50:23,399 ERROR	[6a8400af56192cc745880] decorators:413 - Splunkd daemon is not responding: ('SSL error communicating with splunkd, error="[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1046)", path=/servicesNS/admin/search/search/v2/jobs/export',)
Traceback (most recent call last):
  File "F:\Program Files\Splunk\Python-3.13\Lib\site-packages\splunk\rest\__init__.py", line 855, in streamingRequest
    conn.connect()
    ~~~~~~~~~~~~^^
  File "F:\Program Files\Splunk\Python-3.13\Lib\http\client.py", line 1499, in connect
    self.sock = self._context.wrap_socket(self.sock,
                ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^
                                          server_hostname=server_hostname)
                                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "F:\Program Files\Splunk\Python-3.13\Lib\ssl.py", line 460, in wrap_socket
    return self.sslsocket_class._create(
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        sock=sock,
        ^^^^^^^^^^
    ...<5 lines>...
        session=session
        ^^^^^^^^^^^^^^^
    )
    ^
  File "F:\Program Files\Splunk\Python-3.13\Lib\ssl.py", line 1085, in _create
    self.do_handshake()
    ~~~~~~~~~~~~~~~~~^^
  File "F:\Program Files\Splunk\Python-3.13\Lib\ssl.py", line 1381, in do_handshake
    self._sslobj.do_handshake()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1046)

Splunk (please complete the following information):

  • Version: 10.4.1
  • OS: Windows
  • Deployment: Single Instance Enterprise

SDK (please complete the following information):

  • Version: As per install
  • Language Runtime Version: As per install
  • OS: As per install

Additional context
I think the problem is in Splunk\Python-3.13\Lib\site-packages\splunk\rest\__init__.py, when it goes to create the "conn" object for the connection, it has an if-else statement. In the "if" part of the statement, it has the "if isssl else httplib.HTTPConnection(host, port, timeout=timeout)" code which will create an HTTPConnection if ssl is not enabled. BUT in the "else" part of the if-else statement, it doesn't have that, so will always attempt to create an HTTPSConnection even if ssl is not enabled.

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Start in Splunk\Python-3.13\Lib\site-packages\splunk\rest_init_.py, around streamingRequest and the conn creation logic, then reproduce the export request with enableSplunkdSSL=false. Verify the connection uses the configured protocol and that search-result export succeeds without the WRONG_VERSION_NUMBER error.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
python
Domaine
api
Type d'issue
Bug
Difficulté
3/5
Temps estimé
1-2 jours
Activité
Calme
Clarté
Clairement spécifiée
Accessibilité débutants
74/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.