From f89457a315219b239e415f5aaa062e60d2dee1cc Mon Sep 17 00:00:00 2001
From: Axel Uhl <axel.uhl@sap.com>
Date: Thu, 28 Sep 2017 09:58:45 +0200
Subject: [PATCH] updated release notes for bug 4317

Change-Id: I97f6f22a56697ac9353ebc1cb0ac0840e48a6773
---
 java/com.sap.sailing.www/release_notes_admin.html | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/java/com.sap.sailing.www/release_notes_admin.html b/java/com.sap.sailing.www/release_notes_admin.html
index b2332aa32a1..e8f01e8ca99 100755
--- a/java/com.sap.sailing.www/release_notes_admin.html
+++ b/java/com.sap.sailing.www/release_notes_admin.html
@@ -44,6 +44,13 @@
                               <li><tt>igtimi.client.redirect.port</tt>: redirection port; defaults to empty, using the default port for the protocol</li>
                             </ul>
                         </li>
+                        <li>When using a TracTrac update URI, errors were possible due to the incorrect use of HTTP
+                            instead of HTTPS as the URI/URL's protocol. The TracTrac server responds to an HTTP
+                            request with a response code 302 (temporary redirect), but our TracTrac connector did
+                            not handle this due to redirects that change protocols are not followed by default in
+                            Java. This has now been changed, and although it is of course better to use the correct
+                            protocol (HTTPS) right away, redirects will now be handled correctly, too.
+                        </li>
                     </ul>
 
                     <h2 class="articleSubheadline">August 2017</h2>