[Note] I can't connect with wget, but I can connect with curl

Event

When I launch tomcat in local and access it with wget, it doesn't connect. If you try accessing with curl, you will be connected. Why is it the same access destination?

Cause

It seems that wget has a setting to access via a proxy, which was enabled.

[File]
/etc/wgetrc

[Applicable settings]
http_proxy=http://proxy.xxx.xxx:pp/
https_proxy=http://proxy.xxx.xxx:pp/

Impressions

I used to use wget as I like, but when I look it up, there are quite a few differences between curl and wget. I will omit it because there are other people who have summarized it.

Recommended Posts

[Note] I can't connect with wget, but I can connect with curl
I can't search with # google-map. ..
I can't install python3 with pyenv-vertualenv
I can't download images with Google_images_download
I can't install mysql-connector-python with anaconda
I can't use Japanese with pyperclip
I tried batch normalization with PyTorch (+ note)
I can't deploy with google app engine
I can't install the package with pip.
I can't see new files with yum
I want to send Gmail with Python, but I can't because of an error
When I connect to a remote Jupyter Server with VScode, it's remote but local
I can't install Dask with pip on Ubuntu
Get only Response Header with curl and wget