app/templates/views/email-link-interstitial.html

{% extends "base.html" %}
{% from "components/page-header.html" import page_header %}
{% from "components/page-footer.html" import page_footer %}

{% block per_page_title %}
    Click below to complete email re-verification and finish signing in.
{% endblock %}

{% block maincolumn_content %}

<div>

    <h1 class="font-body-2xl margin-bottom-3">Click below to complete email re-verification and finish signing in.</h1>

  <form method="post" id="use-email-auth">
    {{ page_footer('Verify email') }}
  </form>

</div>

{% endblock %}
replaced content_tempalte and withoutnav_template with base.html 2024-04-24 12:31:00 -07:00			`{% extends "base.html" %}`
Add interstitial page before using email auth token Some email clients will pre-fetch links in emails to check whether they’re safe. This has the unfortunate side effect of claiming the token that’s in the link. Long term, we don’t want to let the link be used multiple times, because this reduces how secure it is (eg someone with access to your browser history could re-use the link even if you’d signed out). Instead, this commit adds an extra page which is served when the user clicks the link from the email. This page includes a form which submits to the actual URL that uses the token, thereby not claiming the token as soon as the page is loaded. For convenience, this page also includes some Javascript which clicks the link on the user’s behalf. If the user has Javascript turned off they will see the link and can click it themselves. This is going on the assumption that whatever the email clients are doing when prefetching the link doesn’t involve running any Javascript. This Javascript is inlined so that: - it is run as fast as possible - it’s more resilient – even if our assets domain is unreachable or the connection is interrupted, it will still run 2020-05-04 12:27:51 +01:00			`{% from "components/page-header.html" import page_header %}`
			`{% from "components/page-footer.html" import page_footer %}`

			`{% block per_page_title %}`
Form is visible in html/text added for clarification on validation 2023-06-14 09:42:22 -06:00			`Click below to complete email re-verification and finish signing in.`
Add interstitial page before using email auth token Some email clients will pre-fetch links in emails to check whether they’re safe. This has the unfortunate side effect of claiming the token that’s in the link. Long term, we don’t want to let the link be used multiple times, because this reduces how secure it is (eg someone with access to your browser history could re-use the link even if you’d signed out). Instead, this commit adds an extra page which is served when the user clicks the link from the email. This page includes a form which submits to the actual URL that uses the token, thereby not claiming the token as soon as the page is loaded. For convenience, this page also includes some Javascript which clicks the link on the user’s behalf. If the user has Javascript turned off they will see the link and can click it themselves. This is going on the assumption that whatever the email clients are doing when prefetching the link doesn’t involve running any Javascript. This Javascript is inlined so that: - it is run as fast as possible - it’s more resilient – even if our assets domain is unreachable or the connection is interrupted, it will still run 2020-05-04 12:27:51 +01:00			`{% endblock %}`

			`{% block maincolumn_content %}`

Form is visible in html/text added for clarification on validation 2023-06-14 09:42:22 -06:00			`<div>`
Add interstitial page before using email auth token Some email clients will pre-fetch links in emails to check whether they’re safe. This has the unfortunate side effect of claiming the token that’s in the link. Long term, we don’t want to let the link be used multiple times, because this reduces how secure it is (eg someone with access to your browser history could re-use the link even if you’d signed out). Instead, this commit adds an extra page which is served when the user clicks the link from the email. This page includes a form which submits to the actual URL that uses the token, thereby not claiming the token as soon as the page is loaded. For convenience, this page also includes some Javascript which clicks the link on the user’s behalf. If the user has Javascript turned off they will see the link and can click it themselves. This is going on the assumption that whatever the email clients are doing when prefetching the link doesn’t involve running any Javascript. This Javascript is inlined so that: - it is run as fast as possible - it’s more resilient – even if our assets domain is unreachable or the connection is interrupted, it will still run 2020-05-04 12:27:51 +01:00
Form is visible in html/text added for clarification on validation 2023-06-14 09:42:22 -06:00			`<h1 class="font-body-2xl margin-bottom-3">Click below to complete email re-verification and finish signing in.</h1>`
Add interstitial page before using email auth token Some email clients will pre-fetch links in emails to check whether they’re safe. This has the unfortunate side effect of claiming the token that’s in the link. Long term, we don’t want to let the link be used multiple times, because this reduces how secure it is (eg someone with access to your browser history could re-use the link even if you’d signed out). Instead, this commit adds an extra page which is served when the user clicks the link from the email. This page includes a form which submits to the actual URL that uses the token, thereby not claiming the token as soon as the page is loaded. For convenience, this page also includes some Javascript which clicks the link on the user’s behalf. If the user has Javascript turned off they will see the link and can click it themselves. This is going on the assumption that whatever the email clients are doing when prefetching the link doesn’t involve running any Javascript. This Javascript is inlined so that: - it is run as fast as possible - it’s more resilient – even if our assets domain is unreachable or the connection is interrupted, it will still run 2020-05-04 12:27:51 +01:00
			`<form method="post" id="use-email-auth">`
Form is visible in html/text added for clarification on validation 2023-06-14 09:42:22 -06:00			`{{ page_footer('Verify email') }}`
Add interstitial page before using email auth token Some email clients will pre-fetch links in emails to check whether they’re safe. This has the unfortunate side effect of claiming the token that’s in the link. Long term, we don’t want to let the link be used multiple times, because this reduces how secure it is (eg someone with access to your browser history could re-use the link even if you’d signed out). Instead, this commit adds an extra page which is served when the user clicks the link from the email. This page includes a form which submits to the actual URL that uses the token, thereby not claiming the token as soon as the page is loaded. For convenience, this page also includes some Javascript which clicks the link on the user’s behalf. If the user has Javascript turned off they will see the link and can click it themselves. This is going on the assumption that whatever the email clients are doing when prefetching the link doesn’t involve running any Javascript. This Javascript is inlined so that: - it is run as fast as possible - it’s more resilient – even if our assets domain is unreachable or the connection is interrupted, it will still run 2020-05-04 12:27:51 +01:00			`</form>`

			`</div>`

			`{% endblock %}`