-
Bug
-
Resolution: Fixed
-
Minor
In version 2.3, the JSON requests are incuding the port number even if it is not needed. For instance, configuring the url to https://jira.example/ will actually make the request of https://jira.example:443/rest/api/latest/mypermissions
In my environment, this is causing the request to fail because JIRA server resets the connection. Yes, I know including the port in a URL is valid. Our JIRA server is not aware of this fact.
This is a regression from 2.2.1. It appears to be connected to the new HTTP components. Changing the version from 4.5.1 back to 4.2.5 solves the problem.