当前位置：文江博客话题详情

cURL Hosts

设置 cURL 使用本地虚拟主机

发布于 2024-09-12 11:42:55 字数 446 浏览 7 评论 0 原文

使用 Apache 或 Ngnix，我总是基于真实项目（例如 http://project1.loc）创建开发站点，在添加到我的 .hosts 文件后，浏览器没有使用时出现问题。

但是，当我尝试向同一 URL 发出 cURL 请求 (http://project1.loc/post.json) 时，除了超时之外，我什么也得不到。我假设 cURL 不关心我的自定义主机，而是直接访问名称服务器以获取其信息。

我该如何解决这个问题？

更新我设置了一个自定义标头“HOST: http://project1.loc”，现在我收到 400 个错误 - 但它们是瞬时所以我假设 cURL 至少正在使用主机文件......

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

赤濁 2024-09-19 11:42:55

实际上，curl 有一个明确的选项： --resolve

--resolve而不是 curl -H 'Host: yada.com' http://127.0.0.1/something

使用 code>curl --resolve 'yada.com:80:127.0.0.1' http://yada.com/something

你问有什么区别吗？

其中，这适用于 HTTPS。假设您的本地服务器有 yada.com 的证书，上面的第一个示例将失败，因为 yada.com 证书与 127.0.0.1< /code> URL 中的主机名。

第二个示例可以正确使用 HTTPS。

本质上，通过 -H 传递“Host”标头确实会将您的主机侵入标头集，但绕过了所有curl 的特定于主机的智能。使用 --resolve 利用所有适用的正常逻辑，但只是假装 DNS 查找在命令行选项中返回了数据。它的工作原理就像/etc/hosts 应该的那样。

注意 --resolve 需要一个端口号，因此对于 HTTPS，您可以使用

curl --resolve 'yada.com:443:127.0.0.1' https://yada.com/something< /代码>

回复收藏 0 原文

森林很绿却致人迷途 2024-09-19 11:42:55

编辑：虽然这是当前接受的答案，但读者可能会发现用户这个其他答案 href="https://stackoverflow.com/users/260371/john-hart">John Hart 更适合他们的需求。根据用户 Ken 的说法，它使用的选项是在版本 7.21.3 中引入的（2010 年 12 月发布，即在此初始答案之后）。

在您编辑的问题中，您使用 URL 作为主机名，而它只需是主机名。

尝试：

curl -H 'Host: project1.loc' http://127.0.0.1/something

其中 project1.loc 只是主机名，127.0.0.1 是目标 IP 地址。

（如果您使用库中的curl而不是在命令行上使用，请确保不要将http://放入Host标头中。）

EDIT: While this is currently accepted answer, readers might find this other answer by user John Hart more adapted to their needs. It uses an option which, according to user Ken, was introduced in version 7.21.3 (which was released in December 2010, i.e. after this initial answer).

In your edited question, you're using the URL as the host name, whereas it needs to be the host name only.

Try:

curl -H 'Host: project1.loc' http://127.0.0.1/something

where project1.loc is just the host name and 127.0.0.1 is the target IP address.

(If you're using curl from a library and not on the command line, make sure you don't put http:// in the Host header.)

回复收藏 0 原文

北斗星光 2024-09-19 11:42:55

为了在尚未通过 DNS 连接的 Apache http 服务器上设置虚拟主机，我喜欢使用：

curl -s --connect-to ::host-name: http://project1.loc/post.json

其中主机名是运行 Web 服务器的计算机的 IP 地址或 DNS 名称。
这也适用于 https 站点。

For setting up virtual hosts on Apache http-servers that are not yet connected via DNS, I like to use:

curl -s --connect-to ::host-name: http://project1.loc/post.json

Where host-name ist the IP address or the DNS name of the machine on which the web-server is running.
This also works well for https-Sites.

回复收藏 0 原文

日久见人心 2024-09-19 11:42:55

使用指向 127.0.0.1 的真实完全限定域名（例如 dev.yourdomain.com），或者尝试编辑正确的主机文件（通常是 /etc/hosts *nix 环境）。

回复收藏 0 原文

冷血 2024-09-19 11:42:55

看来这并不是一个罕见的问题。

首先检查此。

如果这不起作用，您可以在 Windows 上安装本地 DNS 服务器，例如此。配置 Windows 以使用 localhost 作为 DNS 服务器。该服务器可以配置为对您需要的任何假域名具有权威性，并将所有其他请求的请求转发到真实的 DNS 服务器。

我个人认为这有点过头了，不明白为什么主机文件不起作用。但它应该可以解决你遇到的问题。确保您也将常规 DNS 服务器设置为转发器。

回复收藏 0 原文

暗喜 2024-09-19 11:42:55

服务器是否真正收到请求，并且您是否正确处理主机名（别名）？

添加到我的 .hosts 文件后

检查您的网络服务器日志，看看请求是如何进来的...

curl 有选项来转储发送的请求和收到的响应，这称为跟踪，它将保存到文件中。

--trace

如果您缺少主机或标头信息 - 您可以使用配置选项强制这些标头。

我会让curl 请求在命令行上运行，然后尝试在PHP 中实现。

配置选项是

-K/--config

与curl相关的选项在这里

--trace
启用所有传入和传出数据（包括描述信息）的完整跟踪转储到给定的输出文件。使用“-”作为文件名将输出发送到标准输出。

      This option overrides previous uses of -v/--verbose or --trace-ascii.

      If this option is used several times, the last one will be used.

-K/--配置
指定从哪个配置文件读取curl参数。配置文件是一个文本文件，可以在其中写入命令行参数，然后将其使用，就好像它们是在实际中写入的一样
命令行。选项及其参数必须在同一配置文件行上指定，并用空格、冒号、等号或其任意组合分隔（但是，首选分隔符
tor 是等号）。如果参数要包含空格，则必须将参数括在引号内。在双引号内，可以使用以下转义序列：\、\"、\t、\n、
\r 和 \v。任何其他字母之前的反斜杠将被忽略。如果配置行的第一列是“#”字符，则该行的其余部分将被视为注释。每一项只写一个选项
配置文件中的物理行。

      Specify the filename to -K/--config as '-' to make curl read the file from stdin.

      Note that to be able to specify a URL in the config file, you need to specify it using the --url option, and not by simply writing the URL on its own line. So, it could look similar to this:

      url = "http://curl.haxx.se/docs/"

      Long option names can optionally be given in the config file without the initial double dashes.

      When curl is invoked, it always (unless -q is used) checks for a default config file and uses it if found. The default config file is checked for in the following places in this order:

      1) curl tries to find the "home dir": It first checks for the CURL_HOME and then the HOME environment variables. Failing that, it uses getpwuid() on UNIX-like systems (which  returns  the  home  dir
      given the current user in your system). On Windows, it then checks for the APPDATA variable, or as a last resort the '%USERPROFILE%\Application Data'.

      2)  On windows, if there is no _curlrc file in the home dir, it checks for one in the same dir the curl executable is placed. On UNIX-like systems, it will simply try to load .curlrc from the deter-
      mined home dir.

      # --- Example file ---
      # this is a comment
      url = "curl.haxx.se"
      output = "curlhere.html"
      user-agent = "superagent/1.0"

      # and fetch another URL too
      url = "curl.haxx.se/docs/manpage.html"
      -O
      referer = "http://nowhereatall.com/"
      # --- End of example file ---

      This option can be used multiple times to load multiple config files.

Does the server actually get the requests, and are you handling the host name (alias) properly?

after adding to my .hosts file

Check your webserver log, to see how the request came in...

curl has options to dump the request sent, and response received, it is called trace, which will will be saved to a file.

--trace

If you are missing host or header information - you can force those headers with the config option.

I would get the curl request working on the command line, and then try to implement in PHP.

the config option is

-K/--config

the options that are relevant in curl are here

--trace
Enables a full trace dump of all incoming and outgoing data, including descriptive information, to the given output file. Use "-" as filename to have the output sent to stdout.

      This option overrides previous uses of -v/--verbose or --trace-ascii.

      If this option is used several times, the last one will be used.

-K/--config
Specify which config file to read curl arguments from. The config file is a text file in which command line arguments can be written which then will be used as if they were written on the actual
command line. Options and their parameters must be specified on the same config file line, separated by whitespace, colon, the equals sign or any combination thereof (however, the preferred separa-
tor is the equals sign). If the parameter is to contain whitespace, the parameter must be enclosed within quotes. Within double quotes, the following escape sequences are available: \, \", \t, \n,
\r and \v. A backslash preceding any other letter is ignored. If the first column of a config line is a '#' character, the rest of the line will be treated as a comment. Only write one option per
physical line in the config file.

      Specify the filename to -K/--config as '-' to make curl read the file from stdin.

      Note that to be able to specify a URL in the config file, you need to specify it using the --url option, and not by simply writing the URL on its own line. So, it could look similar to this:

      url = "http://curl.haxx.se/docs/"

      Long option names can optionally be given in the config file without the initial double dashes.

      When curl is invoked, it always (unless -q is used) checks for a default config file and uses it if found. The default config file is checked for in the following places in this order:

      1) curl tries to find the "home dir": It first checks for the CURL_HOME and then the HOME environment variables. Failing that, it uses getpwuid() on UNIX-like systems (which  returns  the  home  dir
      given the current user in your system). On Windows, it then checks for the APPDATA variable, or as a last resort the '%USERPROFILE%\Application Data'.

      2)  On windows, if there is no _curlrc file in the home dir, it checks for one in the same dir the curl executable is placed. On UNIX-like systems, it will simply try to load .curlrc from the deter-
      mined home dir.

      # --- Example file ---
      # this is a comment
      url = "curl.haxx.se"
      output = "curlhere.html"
      user-agent = "superagent/1.0"

      # and fetch another URL too
      url = "curl.haxx.se/docs/manpage.html"
      -O
      referer = "http://nowhereatall.com/"
      # --- End of example file ---

      This option can be used multiple times to load multiple config files.

回复收藏 0 原文

听不够的曲调 2024-09-19 11:42:55

发出请求

C:\wnmp\curl>curl.exe --trace-ascii -H 'project1.loc' -d "uuid=d99a49d846d5ae570
667a00825373a7b5ae8e8e2" http://project1.loc/Users/getSettings.xml

向-H 日志文件

== Info: Could not resolve host: 'project1.loc'; Host not found
== Info: Closing connection #0
== Info: About to connect() to project1.loc port 80 (#0)
== Info:   Trying 127.0.0.1... == Info: connected
== Info: Connected to project1.loc (127.0.0.1) port 80 (#0)
=> Send header, 230 bytes (0xe6)
0000: POST /Users/getSettings.xml HTTP/1.1
0026: User-Agent: curl/7.19.5 (i586-pc-mingw32msvc) libcurl/7.19.5 Ope
0066: nSSL/1.0.0a zlib/1.2.3
007e: Host: project1.loc
0092: Accept: */*
009f: Content-Length: 45
00b3: Content-Type: application/x-www-form-urlencoded
00e4: 
=> Send data, 45 bytes (0x2d)
0000: uuid=d99a49d846d5ae570667a00825373a7b5ae8e8e2
<= Recv header, 24 bytes (0x18)
0000: HTTP/1.1 403 Forbidden
<= Recv header, 22 bytes (0x16)
0000: Server: nginx/0.7.66
<= Recv header, 37 bytes (0x25)
0000: Date: Wed, 11 Aug 2010 15:37:06 GMT
<= Recv header, 25 bytes (0x19)
0000: Content-Type: text/html
<= Recv header, 28 bytes (0x1c)
0000: Transfer-Encoding: chunked
<= Recv header, 24 bytes (0x18)
0000: Connection: keep-alive
<= Recv header, 25 bytes (0x19)
0000: X-Powered-By: PHP/5.3.2
<= Recv header, 56 bytes (0x38)
0000: Set-Cookie: SESSION=m9j6caghb223uubiddolec2005; path=/
<= Recv header, 57 bytes (0x39)
0000: P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
<= Recv header, 2 bytes (0x2)
0000: 
<= Recv data, 118 bytes (0x76)
0000: 6b
0004: <html><head><title>HTTP/1.1 403 Forbidden</title></head><body><h
0044: 1>HTTP/1.1 403 Forbidden</h1></body></html>
0071: 0
0074: 
== Info: Connection #0 to host project1.loc left intact
== Info: Closing connection #0

，其中包含：我的主机文件如下所示：

# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

127.0.0.1       localhost
...
...
127.0.0.1   project1.loc

Making a request to

C:\wnmp\curl>curl.exe --trace-ascii -H 'project1.loc' -d "uuid=d99a49d846d5ae570
667a00825373a7b5ae8e8e2" http://project1.loc/Users/getSettings.xml

Resulted in the -H log file containing:

== Info: Could not resolve host: 'project1.loc'; Host not found
== Info: Closing connection #0
== Info: About to connect() to project1.loc port 80 (#0)
== Info:   Trying 127.0.0.1... == Info: connected
== Info: Connected to project1.loc (127.0.0.1) port 80 (#0)
=> Send header, 230 bytes (0xe6)
0000: POST /Users/getSettings.xml HTTP/1.1
0026: User-Agent: curl/7.19.5 (i586-pc-mingw32msvc) libcurl/7.19.5 Ope
0066: nSSL/1.0.0a zlib/1.2.3
007e: Host: project1.loc
0092: Accept: */*
009f: Content-Length: 45
00b3: Content-Type: application/x-www-form-urlencoded
00e4: 
=> Send data, 45 bytes (0x2d)
0000: uuid=d99a49d846d5ae570667a00825373a7b5ae8e8e2
<= Recv header, 24 bytes (0x18)
0000: HTTP/1.1 403 Forbidden
<= Recv header, 22 bytes (0x16)
0000: Server: nginx/0.7.66
<= Recv header, 37 bytes (0x25)
0000: Date: Wed, 11 Aug 2010 15:37:06 GMT
<= Recv header, 25 bytes (0x19)
0000: Content-Type: text/html
<= Recv header, 28 bytes (0x1c)
0000: Transfer-Encoding: chunked
<= Recv header, 24 bytes (0x18)
0000: Connection: keep-alive
<= Recv header, 25 bytes (0x19)
0000: X-Powered-By: PHP/5.3.2
<= Recv header, 56 bytes (0x38)
0000: Set-Cookie: SESSION=m9j6caghb223uubiddolec2005; path=/
<= Recv header, 57 bytes (0x39)
0000: P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
<= Recv header, 2 bytes (0x2)
0000: 
<= Recv data, 118 bytes (0x76)
0000: 6b
0004: <html><head><title>HTTP/1.1 403 Forbidden</title></head><body><h
0044: 1>HTTP/1.1 403 Forbidden</h1></body></html>
0071: 0
0074: 
== Info: Connection #0 to host project1.loc left intact
== Info: Closing connection #0

My hosts file looks like:

# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

127.0.0.1       localhost
...
...
127.0.0.1   project1.loc

回复收藏 0 原文

~没有更多了~