This bug was initially created as a copy of Bug #2159208

I am copying this bug because: 



Description of problem:
I am located behind firewall and have to use HTTP/HTTPS proxy for any outgoing internet connections. Hence I configured proxy setting in /etc/dnf/dnf.conf (proxy=http://<redacted_hostname>:912/). This works for regular installation and updates.
It does not work for:
# dnf copr enable tomkep/epel-extras
command.
The command displays the usual disclaimer and waits for confirmation to continue which is given. The command then hangs for the couple of minutes and timeouts with the following error:
Error: Failed to connect to https://copr.fedorainfracloud.org/coprs/tomkep/epel-extras/repo/epel-9/dnf.repo?arch=x86_64: Network is unreachable

Judging from netstat the command is attempting DIRECT connection to the Internet:
tcp        0      1 172.28.38.82:55956      3.225.109.36:443        SYN_SENT    15594/python3       
which for the above-mentioned reason obviously fails.

Version-Release number of selected component (if applicable):
dnf-data-4.12.0-4.el9.alma.noarch
dnf-4.12.0-4.el9.alma.noarch
dnf-plugins-core-4.1.0-3.el9.noarch

How reproducible:
Always

Actual results:
The command timeouts and fails to setup copr repository.

Expected results:
The command works.

Additional info:
The repository works correctly once the configuration file is put in place by hand.
Found on AlmaLinux 9.1.