Closed daliboris closed 10 months ago
Remove the secure option. The protocol is enough. I tried to make that point clear in the readme. But it should fail with an actionable error.
It's either the deprecated option "secure" or "protocol"
Using only "protocol": "http:"
value leads to different error: Protocol "http:" not supported. Expected "https:"
I don't have HTTPS on my laptop.
Did you set the correct port to use, because the default is 8443?
{
"connectionOptions": {
"basic_auth": {
"user": "admin",
"pass": ""
},
"protocol": "http:",
"host": "localhost",
"port": 8080
}
}
The error indicates that you have a standard exist-db setup listening on both 8080 ('http:') and 8443 ('https:').
@daliboris what happens if you only set
{
"connectionOptions": {
"basic_auth": {
"user": "admin",
"pass": ""
}
}
Re-reading your issue I am confident that you are really only missing to set the port to 8080
. If that works for you I will close the issue.
It turns out that v1.9.0 was used and the issue is fixed with https://github.com/eXist-db/xst/commit/cf75c70844d839342e20030b540cc4ef40c5316a
What happened?
Setting properties
"secure" : false, "protocol": "http:"
in config file raises an error:A different combination of properteis (
"secure" : false, protocol": "https:"
) will raise a diffeent error:If use only
"protocol": "http:"
(withousecure
property) following error occurs:System Information
Relevant shell output
No response