Skip to main content
Webmasters

Return to Answer

added 3 characters in body
Source Link
Tim Fountain
Tim Fountain
  • 4.5k
  • 1
  • 21
  • 19

There's nothing to worry about here, since http://example.com and http://example.com/ are the same URL. The useragent has to include a path in the HTTP request (as per RFC 2616), so what it sends to the server will be GET / in either case. 

If you add the verbose flag to CURL this is quite easy to verify:

$ curl -v http://example.com
* Rebuilt URL to: http://example.com/
* Hostname was NOT found in DNS cache
*   Trying xxx.xxx.xxx.xxx...
* Connected to example.com (xxx.xxx.xxx.xxx) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.38.0
> Host: example.com
> Accept: */*
> 
< HTTP/1.1 200 OK
< Date: Wed, 19 Aug 2015 01:27:48 GMT
* Server Apache/2.4.7 (Ubuntu) is not blacklisted
< Server: Apache/2.4.7 (Ubuntu)
< Vary: Accept-Encoding
< Transfer-Encoding: chunked
< Content-Type: text/html; charset=UTF-8
< 
[Response]

There's nothing to worry about here, since http://example.com and http://example.com/ are the same URL. The useragent has to include a path in the HTTP request (as per RFC 2616), so what it sends to the server will be GET / in either case. If you add the verbose flag to CURL this is quite easy to verify:

$ curl -v http://example.com
* Rebuilt URL to: http://example.com/
* Hostname was NOT found in DNS cache
*   Trying xxx.xxx.xxx.xxx...
* Connected to example.com (xxx.xxx.xxx.xxx) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.38.0
> Host: example.com
> Accept: */*
> 
< HTTP/1.1 200 OK
< Date: Wed, 19 Aug 2015 01:27:48 GMT
* Server Apache/2.4.7 (Ubuntu) is not blacklisted
< Server: Apache/2.4.7 (Ubuntu)
< Vary: Accept-Encoding
< Transfer-Encoding: chunked
< Content-Type: text/html; charset=UTF-8
< 
[Response]

There's nothing to worry about here, since http://example.com and http://example.com/ are the same URL. The useragent has to include a path in the HTTP request (as per RFC 2616), so what it sends to the server will be GET / in either case. 

If you add the verbose flag to CURL this is quite easy to verify:

$ curl -v http://example.com
* Rebuilt URL to: http://example.com/
* Hostname was NOT found in DNS cache
*   Trying xxx.xxx.xxx.xxx...
* Connected to example.com (xxx.xxx.xxx.xxx) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.38.0
> Host: example.com
> Accept: */*
> 
< HTTP/1.1 200 OK
< Date: Wed, 19 Aug 2015 01:27:48 GMT
* Server Apache/2.4.7 (Ubuntu) is not blacklisted
< Server: Apache/2.4.7 (Ubuntu)
< Vary: Accept-Encoding
< Transfer-Encoding: chunked
< Content-Type: text/html; charset=UTF-8
< 
[Response]
Source Link
Tim Fountain
Tim Fountain
  • 4.5k
  • 1
  • 21
  • 19

There's nothing to worry about here, since http://example.com and http://example.com/ are the same URL. The useragent has to include a path in the HTTP request (as per RFC 2616), so what it sends to the server will be GET / in either case. If you add the verbose flag to CURL this is quite easy to verify:

$ curl -v http://example.com
* Rebuilt URL to: http://example.com/
* Hostname was NOT found in DNS cache
*   Trying xxx.xxx.xxx.xxx...
* Connected to example.com (xxx.xxx.xxx.xxx) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.38.0
> Host: example.com
> Accept: */*
> 
< HTTP/1.1 200 OK
< Date: Wed, 19 Aug 2015 01:27:48 GMT
* Server Apache/2.4.7 (Ubuntu) is not blacklisted
< Server: Apache/2.4.7 (Ubuntu)
< Vary: Accept-Encoding
< Transfer-Encoding: chunked
< Content-Type: text/html; charset=UTF-8
< 
[Response]