From 04a20bf66646bc10f219966ad18af8b7bd995c77 Mon Sep 17 00:00:00 2001
From: Artur <artur@vaadin.com>
Date: Wed, 22 Feb 2017 12:21:38 +0200
Subject: Support Vaadin custom protocols in Vaadin-Refresh redirects (#8597)

A login page you want to redirect to is typically in the webapp root,
which you can now refer to as "Vaadin-Refresh: context://login.html"
---
 .../com/vaadin/client/communication/DefaultConnectionStateHandler.java | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'client')

diff --git a/client/src/main/java/com/vaadin/client/communication/DefaultConnectionStateHandler.java b/client/src/main/java/com/vaadin/client/communication/DefaultConnectionStateHandler.java
index af3f229312..f98165b105 100644
--- a/client/src/main/java/com/vaadin/client/communication/DefaultConnectionStateHandler.java
+++ b/client/src/main/java/com/vaadin/client/communication/DefaultConnectionStateHandler.java
@@ -421,7 +421,8 @@ public class DefaultConnectionStateHandler implements ConnectionStateHandler {
                         + "(:\\s*(.*?))?(\\s|$)")
                 .exec(responseText);
         if (refreshToken != null) {
-            WidgetUtil.redirect(refreshToken.getGroup(2));
+            WidgetUtil.redirect(getConnection()
+                    .translateVaadinUri(refreshToken.getGroup(2)));
         } else {
             handleUnrecoverableCommunicationError(
                     "Invalid JSON response from server: " + responseText,
-- 
cgit v1.2.3