The Social Insurance Institution in Poland will only support HTTP/1.1.

Off-topic discussion/chat/argue area with special rules of engagement.
Forum rules
The Off-Topic area is a general community discussion and chat area with special rules of engagement.

Enter, read and post at your own risk. You have been warned!
While our staff will try to guide the herd into sensible directions, this board is a mostly unrestricted zone where almost anything can be discussed, including matters not directly related to the project, technology or similar adjacent topics.

We do, however, require that you:
  • Do not post anything pornographic.
  • Do not post hate speech in the traditional sense of the term.
  • Do not post content that is illegal (including links to protected software, cracks, etc.)
  • Do not post commercial advertisements, SEO links or SPAM posts.
We also ask that you keep strongly polarizing topics like politics and religion to a minimum. This forum is not the right place to discuss such things.
Please do exercise some common sense. How you act here will inevitably influence how you are treated elsewhere.
User avatar
Piotr Kostrzewski
Lunatic
Lunatic
Posts: 304
Joined: 2018-08-14, 15:08

The Social Insurance Institution in Poland will only support HTTP/1.1.

Unread post by Piotr Kostrzewski » 2025-05-05, 09:59

Hello,
Today I read an article in which it is written that the Social Insurance Institution (in Poland) will only support the HTTP/1.1 protocol.
I know that various government and state institutions are sometimes behind in technology, but even with the protocol?
Is it the same with state offices in your countries?
Have a nice week.
Regards,
Piotrek

User avatar
Pentium4User
Board Warrior
Board Warrior
Posts: 1325
Joined: 2019-04-24, 09:38

Re: The Social Insurance Institution in Poland will only support HTTP/1.1.

Unread post by Pentium4User » 2025-05-05, 10:16

Yes, many government stuff is outdated. Some systems run very old software and therefore no current protocols.
IPv6 is one of those things, even TLS was supported rather lately on certain public services.
The profile picture shows my Maico EC30 E ceiling fan.

vannilla
Moon Magic practitioner
Moon Magic practitioner
Posts: 2386
Joined: 2018-05-05, 13:29

Re: The Social Insurance Institution in Poland will only support HTTP/1.1.

Unread post by vannilla » 2025-05-05, 10:52

There is nothing wrong with 1.1. Of all the "outdated" thing they could've done this is harmless.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 37505
Joined: 2011-08-28, 17:27
Location: Motala, SE

Re: The Social Insurance Institution in Poland will only support HTTP/1.1.

Unread post by Moonchild » 2025-05-05, 13:33

There's absolutely nothing wrong with http/1.1 In fact, any non-https connections on the entire internet are http/1.1 because http/2 was made restricted to https only (as part of the push for https everywhere all the time). Yes it was standardized a long time ago. No that doesn't make it unsuitable for anyone to use.
http/1.1 is also perfectly capable of having secure connections with robust TLS encryption.
Not sure why someone would be upset about a service only supporting http/1.1 -- in fact, something can be said about some of the challenges with http/2 and potential security issues with it (e.g. 0-rtt handshakes).
"A dead end street is a place to turn around and go into a new direction" - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
Basilisk-Dev
Lunatic
Lunatic
Posts: 489
Joined: 2022-03-23, 16:41
Location: Chamber of Secrets

Re: The Social Insurance Institution in Poland will only support HTTP/1.1.

Unread post by Basilisk-Dev » 2025-05-06, 02:23

I have a toy fork of NCSA Mosaic that I like to play with at times. I can speak from experience that if a client supports HTTP/1.0, it is very trivial to support HTTP/1.1 at least at a minimal level. Essentially all you need to do is add support for the Host HTTP header. That’s the only mandatory requirement introduced by HTTP/1.1 that wasn’t already present in HTTP/1.0.

Due to the simplicity in updating HTTP/1.0 clients to HTTP/1.1, I see no issues with them dropping HTTP/1.0.
Off-topic:
If you're still using an HTTP/1.0-only client it might be time to join the 21st century.
Moonchild wrote:
2025-05-05, 13:33
http/2 was made restricted to https only (as part of the push for https everywhere all the time).
Off-topic:
Requiring HTTPS for things like a blog, a browser download page, or a webpage with no way to upload data to that page in any type of form at all seems silly to me. I understand the requirement for HTTPS for financial institutions, shopping, etc.
Basilisk Project Owner

viewtopic.php?f=61&p=230756