Tyler Yahn 42863522e5 Update ClientRequest HTTPS determination (#3577) ... * Update ClientRequest HTTPS determination The ClientRequest function will only report a peer port attribute if that peer port differs from the standard 80 for HTTP and 443 for HTTPS. In determining if the request is for HTTPS use the request URL scheme. This is not perfect. If a user doesn't provide a scheme this will not be correctly detected. However, the current approach of checking if the `TLS` field is non-nil will always be wrong, requests made by client ignore this field and it is always nil. Therefore, switching to using the URL field is the best we can do without having already made the request. * Test HTTPS detection for ClientRequest		2023-01-12 16:01:51 -08:00
..
internal	Update ClientRequest HTTPS determination (#3577)	2023-01-12 16:01:51 -08:00
v1.4.0	Add semantic conventions generation Make target (#2758)	2022-04-12 13:40:43 -07:00
v1.5.0	Add semantic conventions generation Make target (#2758)	2022-04-12 13:40:43 -07:00
v1.6.1	Add semantic conventions generation Make target (#2758)	2022-04-12 13:40:43 -07:00
v1.7.0	Add semantic conventions generation Make target (#2758)	2022-04-12 13:40:43 -07:00
v1.8.0	Add semconv/v1.8.0 (#2763)	2022-04-16 01:58:24 -04:00
v1.9.0	Add semconv/v1.9.0 package (#2792)	2022-04-18 10:38:55 -07:00
v1.10.0	Add semconv/v1.10.0 (#2842)	2022-04-22 07:41:28 -07:00
v1.11.0	Add semconv/v1.11.0 (#3009)	2022-07-13 08:45:46 -04:00
v1.12.0	Add semconv/v1.12.0 (#3010)	2022-07-13 09:55:43 -04:00
v1.13.0	Add v1.13 semantic conventions (#3499)	2023-01-05 14:58:42 -08:00
v1.14.0	Generate semconv/v1.14.0 (#3566)	2023-01-06 14:30:32 -08:00
v1.15.0	Generate semconv/v1.15.0 (#3578)	2023-01-08 08:01:08 -08:00
v1.16.0	Generate semconv/v1.16.0 (#3579)	2023-01-08 08:12:25 -08:00
template.j2	replace required by requirementlevel (#3103)	2022-08-22 12:47:11 -04:00