Return-Path: X-Original-To: apmail-roller-user-archive@www.apache.org Delivered-To: apmail-roller-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1D44C1109A for ; Tue, 8 Apr 2014 15:36:34 +0000 (UTC) Received: (qmail 12814 invoked by uid 500); 8 Apr 2014 15:36:33 -0000 Delivered-To: apmail-roller-user-archive@roller.apache.org Received: (qmail 12558 invoked by uid 500); 8 Apr 2014 15:36:31 -0000 Mailing-List: contact user-help@roller.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@roller.apache.org Delivered-To: mailing list user@roller.apache.org Received: (qmail 11059 invoked by uid 99); 8 Apr 2014 15:36:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Apr 2014 15:36:28 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.216.44] (HELO mail-qa0-f44.google.com) (209.85.216.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Apr 2014 15:36:23 +0000 Received: by mail-qa0-f44.google.com with SMTP id hw13so1067636qab.17 for ; Tue, 08 Apr 2014 08:36:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=eBIuLv+y9CZnzFB2T3LWCGNmstn0C/nvQWwzOwdGz0c=; b=cadEDRaep8IBoGAVQ79iqJBkK2fmuZoPRFGzlvEMQuE3hSiOOBDLhBriJGPiMM0xvj xJul4RKxgmwkkBFvzN/UQuiQD41wybPnWsaLKeSDiAMF4hdCP/XrwyKDFYkHcVdq6tv9 kBwz/u8m040mgX46Rk4tUBkAyCNa9ykn/38s/XC5thCCvJlW3gn580TcmnNwELMVm/CD OzmSJ4mvVRSxV/MzmOFRQeEhHeZzvq+r77repFw97Gc0sw77PuKwsWeyAfpUNoX8rCla I0KKy4opxdJiEa8fi/AYyzz2wr4jU89x7cHwGdUmv2IrvrrSVWmQVRiZk/8WA18hcggq oJ5g== X-Gm-Message-State: ALoCoQmmW0Ci82z/IBuOzsa51oUQDCWSFsLkuu28KnEJa0o5JI7n8SEOR/xwv7/dgxqbSA6O6kqk X-Received: by 10.140.101.244 with SMTP id u107mr3785285qge.107.1396971360847; Tue, 08 Apr 2014 08:36:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.96.146.105 with HTTP; Tue, 8 Apr 2014 08:35:40 -0700 (PDT) In-Reply-To: References: <28EDAEF7-BAA9-4F45-888B-3DA4FA91ADCF@raibledesigns.com> <53433E6D.8030107@gmail.com> From: Matt Raible Date: Tue, 8 Apr 2014 09:35:40 -0600 Message-ID: Subject: Re: Absolute URL without scheme prefix To: user Content-Type: multipart/alternative; boundary=001a11c16772b9b74004f689bdb4 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c16772b9b74004f689bdb4 Content-Type: text/plain; charset=UTF-8 I was successful in fixing my base URL by changing it to: Now everything works with both http and https, provided I change iframes (and other embedded URLs) to use // instead of http://. I was unable to get "force HTTPs" to work, either by modifying web.xml or security.xml. For web.xml, I tried adding the following: HTTPS resources /roller-ui/login.rol /roller-ui/register.rol /roller-ui/register!save.rol /roller-ui/profile.rol /roller-ui/profile!save.rol /roller-ui/admin/* /roller-ui/login-redirect.jsp /roller-ui/login-redirect.rol /roller-ui/authoring/userdata /roller-ui/authoring/membersInvite.rol /roller-ui/authoring/membersInvite!save.rol CONFIDENTIAL Once I did this, I was redirected, but to port 8443 instead of 443. To fix this, I changed tomcat/conf/server.xml to the following: After doing this, I received an infinite loop error in my browser. Next, I tried modifying security.xml by adding the following: This seems to intercept forwards as well, so when trying to go to the top-level URL, I was redirected to the following URL and got a infinite loop error again. https://raible.kgbinternet.com/roller-ui/rendering/page/rd It would be nice to force SSL on the editor pages, but it seems impossible with the current setup - unless I do it at the Apache level with mod_rewrite. Cheers, Matt On Tue, Apr 8, 2014 at 8:51 AM, Matt Raible wrote: > After further inspection, it looks like it's working fine on your blog. > I'm guessing this is because you're missing a element, whereas I > have: > > > > > On Tue, Apr 8, 2014 at 8:47 AM, Matt Raible wrote: > >> This seems to get me part of the way there - thanks Glen. >> >> To enable SSL and have it work for embedded iframes, it looks like I'll >> have to change