Skip to content

Using xccProtocol in a CorbTask results in XCC_PROTOCOL instead of XCC-PROTOCOL #627

@grtjn

Description

@grtjn

We have enabled https on certain ports, and needed to switch CorbTask to use xccs. I first tried to use xccProtocol property inside the task, but that resulted in a 403. It took a while before I remembered that you get a 403 Forbidden if you hit an https port in MarkLogic with http. Looking more closely at the JavaExec commandline, I noticed all other properties like xccUsername, xccHostname are correctly translated to XCC-..., but not xccProtocol.

Workaround is to use System.setProperty('XCC-PROTOCOL', 'xccs').

We are using:
mlDataHubVersion=5.5.5
mlCorbVersion=2.4.6

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions