libcurl2rtt包使用DNS问题

发布于 2020-06-18 09:15:44 浏览：1701 订阅该版

4 个回答

liu2guang 认证专家 2020-06-18

这家伙很懒，什么也没写！

aozima 2020-06-18

调网络不抓包，调I2C等时序不上逻辑分析仪，就像电工不用万用表！多用整理的好的文字，比截图更省流量，还能在整理过程中思考。

芋圆源钰 2020-06-19

这家伙很懒，什么也没写！

芋圆源钰 2020-06-19

这家伙很懒，什么也没写！

芋圆源钰 2020-07-01

这家伙很懒，什么也没写！

查了一周,还是老老实实跟代码发先就是一个宏的问题.
```patch
+++ b/source/ekernel/subsys/net/rt-thread/net_tools/netutils-master/libcurl2rtt-latest/curl/curl_config.h
@@ -30,7 +30,7 @@
 #define   HAVE_FCNTL_O_NONBLOCK  1
 
 /* Define to 1 if you have the gethostbyname_r function. */
-#define   HAVE_GETHOSTBYNAME_R  1
+//#define   HAVE_GETHOSTBYNAME_R  1
```

注释后测试已正常:
```
msh />curl --verbose -k --capath ./ [https://www.rt-thread.com/service/rt-thread.txt](https://www.rt-thread.com/service/rt-thread.txt)  
* timeout on name lookup is not supported
*   Trying 118.31.15.152:443...
* TCP_NODELAY set
* Connected to [http://www.rt-thread.com](www.rt-thread.com) () port 443 (#0)
* mbedTLS: Connecting to [http://www.rt-thread.com:443](www.rt-thread.com:443)
* mbedTLS: Set min SSL version to TLS 1.0
* mbedTLS: Handshake complete, cipher is TLS-ECDHE-RSA-WITH-AES-128-GCM-SHA256
* Dumping cert info:
* cert. version     : 3
* serial number     : 06:43:FD:59:D0:4D:C8:94:2F:54:BA:AF:82:55:72:0E
* issuer name       : C=US, O=DigiCert Inc, OU=www.digicert.com, CN=Encryption Everywhere DV TLS CA - G1
* subject name      : CN=www.rt-thread.com
* issued  on        : 2020-06-21 00:00:00
* expires on        : 2021-06-22 12:00:00
* signed using      : RSA with SHA-256
* RSA key size      : 2048 bits
* basic constraints : CA=false
* subject alt name  : [http://www.rt-thread.com](www.rt-thread.com), rt-thread.com
* key usage         : Digital Signature, Key Encipherment
* ext key usage     : TLS Web Server Authentication, TLS Web Client Authentication

* SSL connected
> GET /service/rt-thread.txt HTTP/1.1
> Host: [http://www.rt-thread.com](www.rt-thread.com)
> User-Agent: curl/7.67.0-DEV
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: nginx/1.10.3 (Ubuntu)
< Date: Wed, 01 Jul 2020 07:50:41 GMT
< Content-Type: text/plain
< Content-Length: 267
< Connection: keep-alive
< Last-Modified: Tue, 18 Sep 2018 03:55:48 GMT
< ETag: "10b-5761d43d95900"
< Accept-Ranges: bytes
< Vary: Accept-Encoding
< 
RT-Thread is an open source IoT operating system from China, which has strong scalability: from a tiny kernel running on a tiny core, for example ARM Cortex-M0, or Cortex-M3/4/7, to a rich feature system running on MIPS32, ARM Cortex-A8, ARM Cortex-A9 DualCore etc.
```
发现一个新问题:
直接用ip地址代替rt-thread.com出现301返回码?
```
msh />curl --verbose -k --capath ./ [https://118.31.15.152/service/rt-thread.txt](https://118.31.15.152/service/rt-thread.txt)  
* timeout on name lookup is not supported
*   Trying 118.31.15.152:443...
* TCP_NODELAY set
* Connected to 118.31.15.152 () port 443 (#0)
* mbedTLS: Connecting to 118.31.15.152:443
* mbedTLS: Set min SSL version to TLS 1.0
* mbedTLS: Handshake complete, cipher is TLS-ECDHE-RSA-WITH-AES-256-GCM-SHA384
* Dumping cert info:
* cert. version     : 3
* serial number     : 09:2F:6D:AE:96:EC:D7:D0:24:55:D2:F5:64:20:50:23
* issuer name       : C=US, O=DigiCert Inc, OU=www.digicert.com, CN=RapidSSL RSA CA 2018
* subject name      : CN=*.rt-thread.org
* issued  on        : 2020-06-05 00:00:00
* expires on        : 2021-06-05 12:00:00
* signed using      : RSA with SHA-256
* RSA key size      : 2048 bits
* basic constraints : CA=false
* subject alt name  : *.rt-thread.org, rt-thread.org
* key usage         : Digital Signature, Key Encipherment
* ext key usage     : TLS Web Server Authentication, TLS Web Client Authentication

* SSL connected
> GET /service/rt-thread.txt HTTP/1.1
> Host: 118.31.15.152
> User-Agent: curl/7.67.0-DEV
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Server: nginx/1.10.3 (Ubuntu)
< Date: Wed, 01 Jul 2020 07:43:17 GMT
< Content-Type: text/html
< Content-Length: 194
< Connection: keep-alive
< Location: [https://www.rt-thread.org/service/rt-thread.txt](https://www.rt-thread.org/service/rt-thread.txt)
< Strict-Transport-Security: max-age=1800; includeSubdomains; preload
< 
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.10.3 (Ubuntu)</center>
</body>
</html>
* Connection #0 to host 118.31.15.152 left intact
```