Why doesn't the port change when switching to https?

Question

JSON

Good day, wt. pro. I'm still figuring out how to redirect to https. I found out the following: if I connect to the site via the http protocol and via https, my port remains the same: 80.
In theory, this should not be. The port should change to 443. Hence, as I understand it, all the problems with endless redirects, because the system simply does not see that we have a transition. (Although the browser shows a closed green padlock).
Hence the question: who has already encountered this? How were they treated?

Answer 1

wordpress has a built in rest api. It allows you to create custom queries.
https://wp-kama.ru/handbook/rest/extending/routes-...

Answer 2

Just use the quest ID in the request URL, for example:
Then the URL will be unique for each quest.

Answer 3

If the browser shows a closed green padlock, then the url starts with https:// and the connection was established on port 443 on the server.
How do you observe that the connection port is 80?