Skip to content

Webstandard force no 404#3479

Open
vmcj wants to merge 4 commits intoDOMjudge:mainfrom
vmcj:webstandard_force_no_404
Open

Webstandard force no 404#3479
vmcj wants to merge 4 commits intoDOMjudge:mainfrom
vmcj:webstandard_force_no_404

Conversation

@vmcj
Copy link
Member

@vmcj vmcj commented Feb 28, 2026

Opening as draft first to see what should be changed.

Seems to work, doing this will help us detect other issues such as when the internal ids were mapped to externalids and not all URLs were updated.

@vmcj vmcj force-pushed the webstandard_force_no_404 branch from c7796cc to 5460e17 Compare February 28, 2026 13:17
@vmcj vmcj force-pushed the webstandard_force_no_404 branch from 5460e17 to 6d2b334 Compare February 28, 2026 14:53
@vmcj vmcj marked this pull request as ready for review February 28, 2026 14:54
vmcj added 3 commits February 28, 2026 17:47
Before we always generated the URL even when docs were not configured. This
resulted in a 404.
As we render the links in templates we should know if the resource is available.
It would detect incorrect URLs such as after switching from internal to externalids.
Wget doesn't run the javascript but follows the link used as template.
@vmcj vmcj force-pushed the webstandard_force_no_404 branch from 6d2b334 to f07f1dd Compare February 28, 2026 16:48
@vmcj vmcj requested a review from nickygerritsen March 1, 2026 10:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant