Actions
feature request #8931
closedTaxeditor supports https
Status:
Closed
Priority:
Highest
Assignee:
Category:
taxeditor
Target version:
Start date:
Due date:
% Done:
100%
Estimated time:
Severity:
normal
Description
The Taxeditor seems not able to connect cdm instances via https.
With this configuration:
{
"name" : "edit-test",
"server" : "test.e-taxonomy.eu",
"port" : 443,
"prefix" : "cdmserver/",
"ignoreCdmLibVersion" : true
},
the connection fails because the taxeditor attempts to connect with HTTP instead of HTTPS. The Server response:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>400 Bad Request</title> </head><body> <h1>Bad Request</h1> <p>Your browser sent a request that this server could not understand.<br /> Reason: You're speaking plain HTTP to an SSL-enabled server port.<br /> Instead use the HTTPS scheme to access this URL, please.<br /> </p> <hr> <address>Apache/2.4.10 (Debian) Server at test.e-taxonomy.eu Port 443</address> </body></html>
Conclusions:
- The Taxeditor should be able to detect the required protocol that is to recover from such protocol failures by using the correct protocol after such errors.
- When the server redirects the editor from port 80 (http) to port 443 (https) the editor must follow the redirect and must use the correct protocol (see point 1.)
- Redirects from port 443 (https) to 80 (http) must work also
- The taxeditor needs a place to store information on the required protocol. data on connections is stored in
.cdmLibrary\cdm_remote_servers.jsonthe json object needs to be extended by a protocol field. The taxeditor should update the connection infotmation when a server redirects from http to https or vice verca. - Configuration of HTTP connection is done at two places separately. (
CdmApplicationRemoteConfiguration,CdmServerInfo) There should be a central point for this.
{
"name" : "edit-test",
"server" : "test.e-taxonomy.eu",
"protocol": "https"
"port" : 443,
"prefix" : "cdmserver/",
"ignoreCdmLibVersion" : true
},
Related issues
Actions