REST API breaking over HTTP Calls after we switched to HTTPS

Rashi Saxena

We have moved our JIRA from HTTP to HTTPS following : https://confluence.atlassian.com/jira/integrating-jira-with-apache-using-ssl-203395380.html

Things are working fine on browser, but all our rest api calls are breaking with the error message :

HTTP/1.1 302 Found
Date: Tue, 08 Mar 2016 18:20:56 GMT
Server: Apache/2.2.3 (Oracle)
Location: https://jiraxxxxx/rest/api/2/project/BA/components
Content-Length: 352
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="https://jiraxxxxx/rest/api/2/project/BA/components">here</a>.</p>
<hr>
<address>Apache/2.2.3 (Oracle) Server at jira.xxxxl Port 80</address>
</body></html>

 

It starts to work as soon as we change the url in the curl command to use HTTPS.

 

However we want REST API to be automatically redirected to HTTPS if someone uses HTTP, is that possible ?

 

What config change do we have to do for apache ?

Josh Steckler

If you're using cURL, use the -L flag to follow redirects.