platform inconsistent behavior involving alt-svc #17171
Comments
more infothis was found when testing an issue for a PR #17152 however it still seems very strange that the behivior is diffrent depending on what VM is used. this could be a sign of something else. |
|
|
so this also happened when compiling from source like under the current master branch. (base) user@user-System-Product-Name:~/Desktop/open_source_work/curl$ curl --alt-svc test.txt https://integralblue.com
curl --alt-svc test.txt https://integralblue.com
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://www.integralblue.com/">here</a>.</p>
<hr>
<address>Apache Server at integralblue.com Port 443</address>
</body></html>
curl: (6) Not resolving .onion address (RFC 7686)and on windows we get under the branch from a 3 days ago in a linux VM of the exact same distribution we get (base) user@user-System-Product-Name:~/Desktop/open_source_work/curl$ curl --alt-svc test.txt https://integralblue.com
curl --alt-svc test.txt https://integralblue.com
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://www.integralblue.com/">here</a>.</p>
<hr>
<address>Apache Server at integralblue.com Port 443</address>
</body></html>
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://www.integralblue.com/">here</a>.</p>
<hr>
<address>Apache Server at integralblue.com Port 443</address>
</body></html>runing the code under windows directly gives the same result. (I would rerun on the current version in both VMware and wsl and get back with the results) |
|
if possible maybe we can run the current CI setup on these 2 simple commands? so we can test on all the platform covered by CI and get a comprehensive view of the current behivior |
|
just confirmed on wsl of the current version. |
So you show one invoke that does the expected and then one that does not. The first invoke is thus not very interesting.
Again: details matter. What headers are returned in the first command line, and what does |
|
I am not quite sure how to answer these questions so I am just going to give you the debug output. root@5CD016BMV5:~/curl/build# rm test.txt
root@5CD016BMV5:~/curl/build# ./src/curl --alt-svc test.txt https://integralblue.com --trace first.txt
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://www.integralblue.com/">here</a>.</p>
<hr>
<address>Apache Server at integralblue.com Port 443</address>
</body></html>
root@5CD016BMV5:~/curl/build# ./src/curl --alt-svc test.txt https://integralblue.com --trace second.txt
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://www.integralblue.com/">here</a>.</p>
<hr>
<address>Apache Server at integralblue.com Port 443</address>
</body></html>
root@5CD016BMV5:~/curl/build#and the file contents are included here so you can take a look. again this is from a wsl running on windows10. and again running the same code natively gives a different result. the result might be different if we ran this on window11 but I don't have a good C setup in such a machine. leaving that up to someone else |
|
And what's this second build like? a |
|
@bagder both the same build its just 2 commands on the same machine. Again it's 8.14-dev from like a day ago. Made with cmake But it seems independent of build what so ever. U would get pretty much the same behivior with 7.9 on native windows. The 1 commonality i found is that it matters what the host machine is. Specifically windows10 seems to have this behivior regardless of how u virtualize it. |
|
Can you build with debug enabled and run it with verbose enabled (-v or -vv) and see if it shows any clues?
Now you're just assuming. curl 7.9 did not support --alt-svc. |
I did this
what I did
what I see
it fails on native linux ("(6) cant process .onion") but on windows it works.
more over on a linux VM in windows it also works...
I expected the following
this code to act the same on all platform. either fail on all or work on all.
curl/libcurl version
8.2
8.0
7.8
all showed the same behivior
operating system
ubuntu 2024 tls (both natively on x64 or as a VM on windows with VMware or with WSL)
windows 10
The text was updated successfully, but these errors were encountered: