RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When connecting over proxy to IPv6 host, proxy returns 400 Bad Request because spice-gtk sends the address in the request without the enclosing brackets, e.g.:
CONNECT 1234::1122:33ff:fe44:5566:5900 HTTP/1.0
instead of correct:
CONNECT [1234::1122:33ff:fe44:5566]:5900 HTTP/1.0

Version-Release number of selected component (if applicable):
spice-gtk3-0.26-8.el7.x86_64
glib-networking-2.42.0-1.el7.x86_64
glib2-2.46.2-3.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. run SPICE_PROXY=http://proxy.example.com remote-viewer spice://[ipv6]:port
(ipv6 nor any VM has to be active, error takes place before proxy trying to connect to it)
2.
3.

Actual results:
400 Bad Request

Expected results:
successful connection or different error

Additional info:

Maybe a bug in proxy_lookup_ready() in spice-session.c, but this probably means spice_uri_create() (which returns a string of the form "spice://$host:$port") has the same issue.
Or a bug in wocky-http-proxy.c:create_request(), which could try to use g_inet_address_new_from_string () on g_proxy_address_get_destination_hostname() to make sure it's not an ipv6 address it needs to bracket.

As Christophe said, the problem was missing "[]" around the hostname
Fix was pushed upstream:
ea37f06eaa11b6307c797895aeb85d87d142625a

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2229.html