Skip to content

ci: fail the deploy if HTTP stops redirecting to HTTPS #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PhilippTheServer merged 1 commit into from
Sep 23, 2026
Merged

ci: fail the deploy if HTTP stops redirecting to HTTPS #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .github/workflows/deploy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,3 +50,13 @@ jobs:
- id: deployment
uses: actions/deploy-pages@v4


- name: HTTP must redirect to HTTPS
run: |
for attempt in 1 2 3 4 5 6; do
location=$(curl -sI http://opentaberna.de/ | tr -d '\r' | awk 'tolower($1)=="location:"{print $2}')
[ "$location" = "https://opentaberna.de/" ] && exit 0
sleep 10
done
echo "http://opentaberna.de/ redirects to '${location}', expected https://opentaberna.de/"
exit 1
3 changes: 2 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,8 @@ project-specific structural checks.
Pushes to `main` run `.github/workflows/deploy.yml`. The workflow verifies the
site before it uploads and deploys the GitHub Pages artifact. Pages must use
**GitHub Actions** as its source, with the custom domain `opentaberna.de` and
**Enforce HTTPS** enabled.
**Enforce HTTPS** enabled. After each deploy the workflow checks that
`http://opentaberna.de/` redirects to HTTPS and fails if it does not.

The repository's `CNAME` file is in place. The apex and `www` DNS records can
therefore be added as documented in the project issue; the `wiki` subdomain is
Expand Down
Loading