In the Curl command it seems to lag or something else #20817

Closed
opened 2026-01-31 07:24:52 +00:00 by claunia · 12 comments
Owner

Originally created by @skanda890 on GitHub (Nov 15, 2023).

Windows Terminal version

1.18.2822.0

Windows build number

10.0.22621.2506

Other Software

OS Build Version: 10.0.22621.2506.amd64fre.ni_release.220506-1250
.NET Version: .NET 6.0.23

Steps to reproduce

Type this in Administrator: Windows Power Shell

" curl github.com "

Expected Behavior

It should at least be a response.

Actual Behavior

Still no response.

Originally created by @skanda890 on GitHub (Nov 15, 2023). ### Windows Terminal version 1.18.2822.0 ### Windows build number 10.0.22621.2506 ### Other Software OS Build Version: 10.0.22621.2506.amd64fre.ni_release.220506-1250 .NET Version: .NET 6.0.23 ### Steps to reproduce Type this in Administrator: Windows Power Shell " curl github.com " ### Expected Behavior It should at least be a response. ### Actual Behavior Still no response.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 07:24:52 +00:00
Author
Owner

@lhecker commented on GitHub (Nov 15, 2023):

Your instructions don't involve telnet. Is there something missing?

@lhecker commented on GitHub (Nov 15, 2023): Your instructions don't involve telnet. Is there something missing?
Author
Owner

@skanda890 commented on GitHub (Nov 15, 2023):

Can you check again?

@skanda890 commented on GitHub (Nov 15, 2023): Can you check again?
Author
Owner

@lhecker commented on GitHub (Nov 15, 2023):

What should I check? Your issue description hasn't changed. It just says:

Type this in Administrator: Windows Power Shell

" curl github.com "

There's no mention of telnet. Did you mean curl?

@lhecker commented on GitHub (Nov 15, 2023): What should I check? Your issue description hasn't changed. It just says: > Type this in Administrator: Windows Power Shell > > " curl github.com " There's no mention of telnet. Did you mean curl?
Author
Owner

@lhecker commented on GitHub (Nov 15, 2023):

Ah I see you changed the title... In that case my next question would be:

  • Does typing the command lag, or does it only lag after you press Enter?
  • Does it lag less when you type curl.exe github.com (= with .exe)?
@lhecker commented on GitHub (Nov 15, 2023): Ah I see you changed the title... In that case my next question would be: * Does typing the command lag, or does it only lag after you press Enter? * Does it lag less when you type `curl.exe github.com` (= with `.exe`)?
Author
Owner

@skanda890 commented on GitHub (Nov 15, 2023):

It lags after I press Enter. It doesn't lag when I type .exe after curl. The response of curl github.com still didn't come.

@skanda890 commented on GitHub (Nov 15, 2023): It lags after I press Enter. It doesn't lag when I type .exe after curl. The response of curl github.com still didn't come.
Author
Owner

@lhecker commented on GitHub (Nov 15, 2023):

I'm confident to say that this also not a Windows Terminal issue, unfortunately.

A terminal is basically like a browser: We only do text rendering and the UI around the text, but we don't really have anything to do with application-specific issues like that. It's almost assuredly not us failing you to show a response, but rather curl not actually printing one in the first place. And we basically don't have any control over what curl does.

If I were you, I'd try to change my IP address and test my internet speed. I'd also never use curl, but only curl.exe, because as I said in the other issue, curl is an alias for Invoke-WebRequest, which is not the same as the true curl. The true curl is vastly superior and much faster, so I'd always use that.

If you want to make sure that it's really not due to Windows Terminal, you can try this:

  • Press Win+R
  • Type conhost powershell.exe and press Enter
  • Type curl.exe github.com and press Enter

If it also lags there then this is not a Windows Terminal issue. If it doesn't lag however, then please try it again in Windows Terminal. If it only lags in Windows Terminal and doesn't lag in "conhost", then please reopen this issue.

@lhecker commented on GitHub (Nov 15, 2023): I'm confident to say that this also not a Windows Terminal issue, unfortunately. A terminal is basically like a browser: We only do text rendering and the UI around the text, but we don't really have anything to do with application-specific issues like that. It's almost assuredly not us failing you to show a response, but rather `curl` not actually printing one in the first place. And we basically don't have any control over what `curl` does. If I were you, I'd try to change my IP address and test my internet speed. I'd also never use `curl`, but only `curl.exe`, because as I said in the other issue, `curl` is an alias for `Invoke-WebRequest`, which is not the same as the true [curl](https://curl.se/). The true curl is vastly superior and much faster, so I'd always use that. If you want to make sure that it's really not due to Windows Terminal, you can try this: * Press Win+R * Type `conhost powershell.exe` and press Enter * Type `curl.exe github.com` and press Enter If it also lags there then this is not a Windows Terminal issue. If it doesn't lag however, then please try it again in Windows Terminal. If it only lags in Windows Terminal and doesn't lag in "conhost", then please reopen this issue.
Author
Owner

@skanda890 commented on GitHub (Nov 15, 2023):

Oh, okay.

@skanda890 commented on GitHub (Nov 15, 2023): Oh, okay.
Author
Owner

@lhecker commented on GitHub (Nov 15, 2023):

The response of curl github.com still didn't come.

You know what, I think I just realized what you meant with "response didn't come"... You didn't mean that curl.exe hangs right? You just meant that there's no visible output?

Try typing this:

curl.exe -v github.com

-v stands for verbose (= detailed) mode. That way, curl will tell you exactly what it does under the hood. You'll then see:

*   Trying 140.82.121.3:80...
* Connected to github.com (140.82.121.3) port 80 (#0)
> GET / HTTP/1.1
> Host: github.com
> User-Agent: curl/8.0.1
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Content-Length: 0
< Location: https://github.com/
<
* Connection #0 to host github.com left intact

In other words, you're being redirected and there's no other response from github (= no text). There's two solutions to this:

  • Use the proper, redirected URL: curl.exe https://github.com/
  • Use -L which stands for "follow redirects" (The curl documentation is super helpful!)

I'd suggest doing the former in this case, because that way you only do 1 request instead of 2.

@lhecker commented on GitHub (Nov 15, 2023): > The response of curl github.com still didn't come. You know what, I think I just realized what you meant with "response didn't come"... You didn't mean that curl.exe hangs right? You just meant that there's no visible output? Try typing this: ``` curl.exe -v github.com ``` `-v` stands for verbose (= detailed) mode. That way, curl will tell you exactly what it does under the hood. You'll then see: ``` * Trying 140.82.121.3:80... * Connected to github.com (140.82.121.3) port 80 (#0) > GET / HTTP/1.1 > Host: github.com > User-Agent: curl/8.0.1 > Accept: */* > < HTTP/1.1 301 Moved Permanently < Content-Length: 0 < Location: https://github.com/ < * Connection #0 to host github.com left intact ``` In other words, you're being redirected and there's no other response from github (= no text). There's two solutions to this: * Use the proper, redirected URL: `curl.exe https://github.com/` * Use `-L` which stands for "follow redirects" (The curl documentation is super helpful!) I'd suggest doing the former in this case, because that way you only do 1 request instead of 2.
Author
Owner

@skanda890 commented on GitHub (Nov 15, 2023):

I'm confident to say that this also not a Windows Terminal issue, unfortunately.

A terminal is basically like a browser: We only do text rendering and the UI around the text, but we don't really have anything to do with application-specific issues like that. It's almost assuredly not us failing you to show a response, but rather curl not actually printing one in the first place. And we basically don't have any control over what curl does.

If I were you, I'd try to change my IP address and test my internet speed. I'd also never use curl, but only curl.exe, because as I said in the other issue, curl is an alias for Invoke-WebRequest, which is not the same as the true curl. The true curl is vastly superior and much faster, so I'd always use that.

If you want to make sure that it's really not due to Windows Terminal, you can try this:

  • Press Win+R
  • Type conhost powershell.exe and press Enter
  • Type curl.exe github.com and press Enter

If it also lags there then this is not a Windows Terminal issue. If it doesn't lag however, then please try it again in Windows Terminal. If it only lags in Windows Terminal and doesn't lag in "conhost", then please reopen this issue.

It lagged.

@skanda890 commented on GitHub (Nov 15, 2023): > I'm confident to say that this also not a Windows Terminal issue, unfortunately. > > A terminal is basically like a browser: We only do text rendering and the UI around the text, but we don't really have anything to do with application-specific issues like that. It's almost assuredly not us failing you to show a response, but rather `curl` not actually printing one in the first place. And we basically don't have any control over what `curl` does. > > If I were you, I'd try to change my IP address and test my internet speed. I'd also never use `curl`, but only `curl.exe`, because as I said in the other issue, `curl` is an alias for `Invoke-WebRequest`, which is not the same as the true [curl](https://curl.se/). The true curl is vastly superior and much faster, so I'd always use that. > > If you want to make sure that it's really not due to Windows Terminal, you can try this: > > * Press Win+R > * Type `conhost powershell.exe` and press Enter > * Type `curl.exe github.com` and press Enter > > If it also lags there then this is not a Windows Terminal issue. If it doesn't lag however, then please try it again in Windows Terminal. If it only lags in Windows Terminal and doesn't lag in "conhost", then please reopen this issue. It lagged.
Author
Owner

@skanda890 commented on GitHub (Nov 15, 2023):

The response of curl github.com still didn't come.

You know what, I think I just realized what you meant with "response didn't come"... You didn't mean that curl.exe hangs right? You just meant that there's no visible output?

Try typing this:

curl.exe -v github.com

-v stands for verbose (= detailed) mode. That way, curl will tell you exactly what it does under the hood. You'll then see:

*   Trying 140.82.121.3:80...
* Connected to github.com (140.82.121.3) port 80 (#0)
> GET / HTTP/1.1
> Host: github.com
> User-Agent: curl/8.0.1
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Content-Length: 0
< Location: https://github.com/
<
* Connection #0 to host github.com left intact

In other words, you're being redirected and there's no other response from github (= no text). There's two solutions to this:

  • Use the proper, redirected URL: curl.exe https://github.com/
  • Use -L which stands for "follow redirects" (The curl documentation is super helpful!)

I'd suggest doing the former in this case, because that way you only do 1 request instead of 2.

Can you tell me the final URL? Yes, I meant that, and the response which was shown above was correct.

@skanda890 commented on GitHub (Nov 15, 2023): > > The response of curl github.com still didn't come. > > You know what, I think I just realized what you meant with "response didn't come"... You didn't mean that curl.exe hangs right? You just meant that there's no visible output? > > Try typing this: > > ``` > curl.exe -v github.com > ``` > > `-v` stands for verbose (= detailed) mode. That way, curl will tell you exactly what it does under the hood. You'll then see: > > ``` > * Trying 140.82.121.3:80... > * Connected to github.com (140.82.121.3) port 80 (#0) > > GET / HTTP/1.1 > > Host: github.com > > User-Agent: curl/8.0.1 > > Accept: */* > > > < HTTP/1.1 301 Moved Permanently > < Content-Length: 0 > < Location: https://github.com/ > < > * Connection #0 to host github.com left intact > ``` > > In other words, you're being redirected and there's no other response from github (= no text). There's two solutions to this: > > * Use the proper, redirected URL: `curl.exe https://github.com/` > * Use `-L` which stands for "follow redirects" (The curl documentation is super helpful!) > > I'd suggest doing the former in this case, because that way you only do 1 request instead of 2. Can you tell me the final URL? Yes, I meant that, and the response which was shown above was correct.
Author
Owner

@lhecker commented on GitHub (Nov 15, 2023):

It's here

< Location: https://github.com/

So it's https://github.com/

@lhecker commented on GitHub (Nov 15, 2023): It's here ``` < Location: https://github.com/ ``` So it's `https://github.com/`
Author
Owner

@skanda890 commented on GitHub (Nov 15, 2023):

Huh, I didn't understand anything, so can you explain this?

@skanda890 commented on GitHub (Nov 15, 2023): Huh, I didn't understand anything, so can you explain this?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20817