Windows socket error требуемый адрес для своего контекста неверен

from socket import *
soc = socket(AF_INET, SOCK_STREAM)
soc.connect(('168.62.48.183', 80))
soc.send('GET /miners/get?file=BFGMiner-3.99-r.1-win32.zip HTTP/1.1nUser-Agent:MultiMiner/V3nHost: www.multiminerapp.comn')
with open("http-response.txt","w") as respfile:
    response = soc.recv(1024) # <--- Use select.epoll or asyncore instead!
    respfile.writelines(response)

The reason for why your code fails tho is because you’re trying to bind to an external IP.
Your machine is not aware of this IP hence the error message, if you’d change it to say 127.0.0.1 it would work, but then again you would need a .listen(4) and ns, na = soc.accept() before utelizing .send() and your soc.recv() would need to be ns.recv(1024).

In other words, you mixed up client sockets with server sockets and you’re binding to a IP not present on the local machine.

Also note: soc.recv() will fail, you need a buffer-size argument like so: soc.recv(1024)

Python3:

from socket import *
soc = socket(AF_INET, SOCK_STREAM)
soc.connect(('168.62.48.183', 80))
soc.send(b'GET /miners/get?file=BFGMiner-3.99-r.1-win32.zip HTTP/1.1nUser-Agent:MultiMiner/V3nHost: www.multiminerapp.comnn') # Note the double nn at the end.
with open("http-response.txt","wb") as respfile:
    response = soc.recv(8192)
    respfile.write(response)

There’s two major differences, we send a binary GET /miners/.. string rather than a standard string.
Secondly we open the output-file in a binary form because the data recieved will also be in binary form..

This is because Python no longer decodes the string for you because of a number of reasons, so you need to either treat the data as binary or manually decode it along the way.

You should probably:

import urllib.request
f = urllib.request.urlopen("http://www.multiminerapp.com/miners/get?file=BFGMiner-3.99-r.1-win32.zip")
print(f.read())

Вам помог наш сайт?

Тогда и мы с радостью примем Вашу помощь
Перечислите любую сумму на Билайн-номер +7-777-398-41-00

Каждое перечисление поможет форуму!

Новые сообщения:

Кто что читает?
Кайрат-F2
03 фев 2023, 16:21

Льготное автокредитование в Казахстане
Кайрат-F2
03 фев 2023, 14:18

[01.02.2023 обновлена] Шаблоны форм на 2023 год для ИС СОНО
Кайрат-F2
01 фев 2023, 17:50

[01.02.2023 обновлена] Шаблоны форм на 2022 год для ИС СОНО
Кайрат-F2
01 фев 2023, 17:48

[01.02.2023 обновлена] Шаблоны форм на 2021 год для ИС СОНО
Кайрат-F2
01 фев 2023, 17:48

[01.02.2023 обновлена] Шаблоны форм на 2020 год для ИС СОНО
Кайрат-F2
01 фев 2023, 17:47

Работа сайта и форума bb.f2.kz
Кайрат-F2
01 фев 2023, 15:19

[01.02.2023 обновлена] Правила заполнения налоговых форм на 2019 год
Кайрат-F2
01 фев 2023, 00:16

[01.02.2023 обновлена] Правила заполнения налоговых форм на 2018 год
Кайрат-F2
01 фев 2023, 00:16

Предельные цены на нефтепродукты в Казахстане
Кайрат-F2
31 янв 2023, 17:51

[30.01.2023 обновлена] Правила заполнения налоговых форм на 2017 год
Кайрат-F2
30 янв 2023, 15:36

Девальвация или инфляция в Казахстане?
Кайрат-F2
28 янв 2023, 10:13

Угрозы неожиданно низкой инфляции при сокращении спроса
Кайрат-F2
28 янв 2023, 10:09

Хорошие новости и хорошие инициативы
Кайрат-F2
27 янв 2023, 22:37

Аргентина, Бразилия и Договор Тлателолько
Кайрат-F2
25 янв 2023, 17:57

Форма 701.01 2018 год [Расчёт текущих платежей]
daur
20 янв 2023, 11:30

Отчеты:внутренние, статистические, финансовые
daur
19 янв 2023, 16:35

www.esf.gov.kz — Портал по выписке электронных счетов-фактур
Кайрат-F2
16 янв 2023, 22:36

Работа налоговых серверов в 1 квартале 2023 года
Кайрат-F2
15 янв 2023, 18:50

Я и моя машина, наши железные друзья
Кайрат-F2
13 янв 2023, 21:01

Проблемы образования.
Кайрат-F2
13 янв 2023, 20:57

[21.12.2022 обновлена] Версия ИС СОНО 4.0.33 [15.12.2022]
daur
08 янв 2023, 13:38

Новогодняя тема
Necytij
31 дек 2022, 19:54

AKMedia Browser 21.5.2 [ЭСФ, обновление форм СОНО, Кабинет]
daur
24 дек 2022, 22:54

[23.12.2022 обновлена] AKMedia Browser 22.12.23[ЭСФ, обновление форм СОНО, Кабинет]
Кайрат-F2
23 дек 2022, 20:00

Фильм «Откочевники мертвой степи» Досыма Сатпаева
Кайрат-F2
22 дек 2022, 18:05

This is not really specific to Unity but rather c# in general.

Socket.Bind is for binding the socket to a specific local endpoint! Such as for example you want to limit the socket to a specific local network adapter / address (by default it will use any/all) or a specific local port (by default it will pick any free local port)

Use the Bind method if you need to use a specific local endpoint. You must call Bind before you can call the Listen method. You do not need to call Bind before using the Connect method unless you need to use a specific local endpoint.

Usually you use Bind mostly for the server side for listening and waiting for incoming connections or for connectionless protocols like UDP.

You most probably simply want to rather use Socket.Connect for establishing a connection to a remote server.

When using Connect without Bind then it will simply pick the network adapter / address it finds to be the best fit for reaching the given host address and picks the next free local port.

However, in general I would recommend to rather use TcpClient instead of composing and configuring the Socket «manually» (except the use case requires it).

var tcpClient = new TcpClient(sHostIpAddress, nPort);

This constructor will automatically start a connection attempt. TcpClient is an IDisposable and cleans up the underlying socket, stream etc when it is disposed. It also is (in my eyes) way easier to configure and to sent and receive data with it.

This is not really specific to Unity but rather c# in general.

Socket.Bind is for binding the socket to a specific local endpoint! Such as for example you want to limit the socket to a specific local network adapter / address (by default it will use any/all) or a specific local port (by default it will pick any free local port)

Use the Bind method if you need to use a specific local endpoint. You must call Bind before you can call the Listen method. You do not need to call Bind before using the Connect method unless you need to use a specific local endpoint.

Usually you use Bind mostly for the server side for listening and waiting for incoming connections or for connectionless protocols like UDP.

You most probably simply want to rather use Socket.Connect for establishing a connection to a remote server.

When using Connect without Bind then it will simply pick the network adapter / address it finds to be the best fit for reaching the given host address and picks the next free local port.

However, in general I would recommend to rather use TcpClient instead of composing and configuring the Socket «manually» (except the use case requires it).

var tcpClient = new TcpClient(sHostIpAddress, nPort);

This constructor will automatically start a connection attempt. TcpClient is an IDisposable and cleans up the underlying socket, stream etc when it is disposed. It also is (in my eyes) way easier to configure and to sent and receive data with it.

TcpClient

0 пользователей читают эту тему (0 гостей и 0 скрытых пользователей)

0 пользователей: