Wait pages like this are nonsense. If the server has capacity to show you this it could just show you the content you are looking for. Its obvious artificial rate limiting.
not really; that page is much simpler to process and upload than an entire pedophile archive
sharing anything over the internet takes resources, in this case a lot of them, and with government infrastructure they’re sometimes far behind the modern day trends on purpose, for stability/reliability reasons.
Also caching is a factor here. Search results in particular can be a nightmare since variations in spelling or query string parameters having a difference of a single character makes it different than what others previously searched.
Not nessissarially true, very likely the wait page is rendered from cached memory and does not require a ssd read to print whereas any actual files would. It is true that the web server does have to have capacity to show you this, but I’m pretty sure the limitation will be on the SSD side. (Read and write operations). Source 5 years webserver admin.
Wait pages like this are nonsense. If the server has capacity to show you this it could just show you the content you are looking for. Its obvious artificial rate limiting.
The servers that serve the content are very often different servers from serving the web site.
You clearly have never worked on tech at real scale.
not really; that page is much simpler to process and upload than an entire pedophile archive
sharing anything over the internet takes resources, in this case a lot of them, and with government infrastructure they’re sometimes far behind the modern day trends on purpose, for stability/reliability reasons.
There is also usually a load balancer in front of the actual application servers, so the page is probably being served by that instead
VPS with reverse proxy in front of a Raspberry Pi type shit.
Also caching is a factor here. Search results in particular can be a nightmare since variations in spelling or query string parameters having a difference of a single character makes it different than what others previously searched.
The other interesting thing is you only have 10 minutes when you get in to grab your stuff and go
Not nessissarially true, very likely the wait page is rendered from cached memory and does not require a ssd read to print whereas any actual files would. It is true that the web server does have to have capacity to show you this, but I’m pretty sure the limitation will be on the SSD side. (Read and write operations). Source 5 years webserver admin.
Interestingly, if someone links you to one of the files directly, there is no wait or redirect to the wait page.
Which means they have no actual issue with content delivery, else they would limit that too.
I think you might be overlooking human error in configuration.
On a government site? Inconceivable.