You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
connect-tcp makes the target_host variable a list, which is a feature that connect-udp didn't have. I'm not an expert of URI templates, but this doesn't seem correct. The feature definition links to composite values from RFC 6570, but those require a * in the template - which is something that the document does not use in its examples nor the default template. Additionally, an example in connect-tcp uses :path = /proxy?target_host=192.0.2.1,2001:db8::1&tcp_port=443 whereas the notation from RFC 6570 would be :path = /proxy?target_host=192.0.2.1&target_host=2001:db8::1&tcp_port=443
The text was updated successfully, but these errors were encountered:
connect-tcp makes the target_host variable a list, which is a feature that connect-udp didn't have. I'm not an expert of URI templates, but this doesn't seem correct. The feature definition links to composite values from RFC 6570, but those require a
*
in the template - which is something that the document does not use in its examples nor the default template. Additionally, an example in connect-tcp uses:path = /proxy?target_host=192.0.2.1,2001:db8::1&tcp_port=443
whereas the notation from RFC 6570 would be:path = /proxy?target_host=192.0.2.1&target_host=2001:db8::1&tcp_port=443
The text was updated successfully, but these errors were encountered: