<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>My first thought is...<br>
    </p>
    <p><a class="moz-txt-link-freetext"
        href="https://metacpan.org/pod/Catalyst#PROXY-SUPPORT">https://metacpan.org/pod/Catalyst#PROXY-SUPPORT</a></p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 02/10/2021 14:35, Chris Welch wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAAee2CO-CqaEVirRdq-naA5hHrRMiRN13drXSNf2QxH_OkqQOw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div class="gmail_default"
          style="font-family:tahoma,sans-serif;color:#000066">Hi
          everyone</div>
        <div class="gmail_default"
          style="font-family:tahoma,sans-serif;color:#000066"><br>
        </div>
        <div class="gmail_default"
          style="font-family:tahoma,sans-serif;color:#000066">In my
          infinite(!) wisdom, I decided to do a complete server rebuild
          before people will start using my website again next month. 
          This previously was working correctly, however now even though
          the page is being served over https, all the links (which use
          $c-&gt;uri_for and $c-&gt;uri_for_action) are returning http
          versions, which is causing the style sheets to fail to load
          for one thing, but also form submissions are going over http.</div>
        <div class="gmail_default"
          style="font-family:tahoma,sans-serif;color:#000066"><br>
        </div>
        <div class="gmail_default"
          style="font-family:tahoma,sans-serif;color:#000066">Some
          things that may be pertinent:</div>
        <div class="gmail_default"
          style="font-family:tahoma,sans-serif;color:#000066"><br>
        </div>
        <div class="gmail_default"
          style="font-family:tahoma,sans-serif;color:#000066">
          <ul>
            <li>Using nginx / Starman (same as before).</li>
            <li>This is using a letsencrypt certificate, which it was
              before, but when I set it up before there wasn't a certbot
              to automate it, so it was done manually.</li>
            <li>Website in case it's useful: <a
                href="https://www.mkttl.co.uk/" moz-do-not-send="true">https://www.mkttl.co.uk/</a></li>
            <li>Catalyst version is now the latest - previously I
              *think* it was 5.90118, but unfortunately can't be sure.</li>
          </ul>
          <div>Thank you in advance for any suggestions!</div>
          <div><br>
          </div>
          <div><br>
          </div>
          <div>Chris</div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
List: <a class="moz-txt-link-abbreviated" href="mailto:Catalyst@lists.scsys.co.uk">Catalyst@lists.scsys.co.uk</a>
Listinfo: <a class="moz-txt-link-freetext" href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst">http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst</a>
Searchable archive: <a class="moz-txt-link-freetext" href="http://www.mail-archive.com/catalyst@lists.scsys.co.uk/">http://www.mail-archive.com/catalyst@lists.scsys.co.uk/</a>
Dev site: <a class="moz-txt-link-freetext" href="http://dev.catalyst.perl.org/">http://dev.catalyst.perl.org/</a>
</pre>
    </blockquote>
  </body>
</html>