求大蝦來指導(dǎo)！

cz_huangji

use IO::Socket;
$sock = IO::Socket::INET->new ('172.16.6.37:80')
  or die "Socket could not be created.Because $!\n" unless $sock;
$sock->send("GET HTTP/1.1",0);

$data = <$sock>;
print $data;
close $sock;

為什么得不到服務(wù)端回顯的信息呢？
PS：新手，還望手下留情啊～～

Namelessxp

1. 
   
2. $sock->send("GET / HTTP/1.1\r\nHost:172.16.6.37\r\n\r\n\r\n",0);
   

復(fù)制代碼

cz_huangji

謝樓上！
可以看到HTTP/1.1 200 OK的字樣了
假如我要請求一個頁面或文件，又應(yīng)該怎么寫呢？（http://172.16.6.37/test/test.html)

PS:還是沒把HTTP header看懂�。�

flw

原帖由 Namelessxp 于 2006-11-26 22:23 發(fā)表

1. 
   
2. $sock->send("GET / HTTP/1.1\r\nHost:172.16.6.37\r\n\r\n\r\n",0);
   

復(fù)制代碼

\r\n 是錯誤的。是不可移植的。正確的寫法是直接用 \x0d \x0a 或者用模塊導(dǎo)出的 CRLF

cz_huangji

原帖由 flw 于 2006-11-26 22:33 發(fā)表

\r\n 是錯誤的。是不可移植的。正確的寫法是直接用 \x0d \x0a 或者用模塊導(dǎo)出的 CRLF

這個姐姐更專業(yè)！！

cz_huangji

原帖由 Namelessxp 于 2006-11-26 22:23 發(fā)表

1. 
   
2. $sock->send("GET /test/test.html HTTP/1.1\r\nHost:172.16.6.37\r\n\r\n\r\n",0);
   

復(fù)制代碼

我照著改了一下就搞定了！！
呵呵，，

Namelessxp

原帖由 flw 于 2006-11-26 22:33 發(fā)表

\r\n 是錯誤的。是不可移植的。正確的寫法是直接用 \x0d \x0a 或者用模塊導(dǎo)出的 CRLF

這個倒沒大注意,目前不管PHP還是Perl都是在Win平臺下運行,看來是個隱患,受教

flw

原帖由 Namelessxp 于 2006-11-27 08:19 發(fā)表

這個倒沒大注意,目前不管PHP還是Perl都是在Win平臺下運行,看來是個隱患,受教

以下內(nèi)容摘錄自 perldoc perlport：

1. Newlines
   
2. 
   
3. In most operating systems, lines in files are terminated by newlines. Just what is used as a newline may vary from OS to OS. Unix traditionally uses \012, one type of DOSish I/O uses \015\012, and Mac OS uses \015.
   
4. 
   
5. Perl uses \n to represent the ``logical'' newline, where what is logical may depend on the platform in use. In MacPerl, \n always means \015. In DOSish perls, \n usually means \012, but when accessing a file in ``text'' mode, STDIO translates it to (or from) \015\012, depending on whether you're reading or writing. Unix does the same thing on ttys in canonical mode. \015\012 is commonly referred to as CRLF.
   
6. 
   
7. A common cause of unportable programs is the misuse of chop() to trim newlines:
   
8. 
   
9.     # XXX UNPORTABLE!
   
10.     while(<FILE>) {
    
11.         chop;
    
12.         @array = split(/:/);
    
13.         #...
    
14.     }
    
15. 
    
16. You can get away with this on Unix and Mac OS (they have a single character end-of-line), but the same program will break under DOSish perls because you're only chop()ing half the end-of-line. Instead, chomp() should be used to trim newlines. The the Dunce::Files manpage module can help audit your code for misuses of chop().
    
17. 
    
18. When dealing with binary files (or text files in binary mode) be sure to explicitly set $/ to the appropriate value for your file format before using chomp().
    
19. 
    
20. Because of the ``text'' mode translation, DOSish perls have limitations in using seek and tell on a file accessed in ``text'' mode. Stick to seek-ing to locations you got from tell (and no others), and you are usually free to use seek and tell even in ``text'' mode. Using seek or tell or other file operations may be non-portable. If you use binmode on a file, however, you can usually seek and tell with arbitrary values in safety.
    
21. 
    
22. A common misconception in socket programming is that \n eq \012 everywhere. When using protocols such as common Internet protocols, \012 and \015 are called for specifically, and the values of the logical \n and \r (carriage return) are not reliable.
    
23. 
    
24.     print SOCKET "Hi there, client!\r\n";      # WRONG
    
25.     print SOCKET "Hi there, client!\015\012";  # RIGHT
    
26. 
    
27. However, using \015\012 (or \cM\cJ, or \x0D\x0A) can be tedious and unsightly, as well as confusing to those maintaining the code. As such, the Socket module supplies the Right Thing for those who want it.
    
28. 
    
29.     use Socket qw(:DEFAULT :crlf);
    
30.     print SOCKET "Hi there, client!$CRLF"      # RIGHT
    
31. 
    
32. When reading from a socket, remember that the default input record separator $/ is \n, but robust socket code will recognize as either \012 or \015\012 as end of line:
    
33. 
    
34.     while (<SOCKET>) {
    
35.         # ...
    
36.     }
    
37. 
    
38. Because both CRLF and LF end in LF, the input record separator can be set to LF and any CR stripped later. Better to write:
    
39. 
    
40.     use Socket qw(:DEFAULT :crlf);
    
41.     local($/) = LF;      # not needed if $/ is already \012
    
42. 
    
43.     while (<SOCKET>) {
    
44.         s/$CR?$LF/\n/;   # not sure if socket uses LF or CRLF, OK
    
45.     #   s/\015?\012/\n/; # same thing
    
46.     }
    
47. 
    
48. This example is preferred over the previous one--even for Unix platforms--because now any \015's (\cM's) are stripped out (and there was much rejoicing).
    
49. 
    
50. Similarly, functions that return text data--such as a function that fetches a web page--should sometimes translate newlines before returning the data, if they've not yet been translated to the local newline representation. A single line of code will often suffice:
    
51. 
    
52.     $data =~ s/\015?\012/\n/g;
    
53.     return $data;
    
54. 
    
55. Some of this may be confusing. Here's a handy reference to the ASCII CR and LF characters. You can print it out and stick it in your wallet.
    
56. 
    
57.     LF  eq  \012  eq  \x0A  eq  \cJ  eq  chr(10)  eq  ASCII 10
    
58.     CR  eq  \015  eq  \x0D  eq  \cM  eq  chr(13)  eq  ASCII 13
    
59. 
    
60.              | Unix | DOS  | Mac  |
    
61.         ---------------------------
    
62.         \n   |  LF  |  LF  |  CR  |
    
63.         \r   |  CR  |  CR  |  LF  |
    
64.         \n * |  LF  | CRLF |  CR  |
    
65.         \r * |  CR  |  CR  |  LF  |
    
66.         ---------------------------
    
67.         * text-mode STDIO
    
68. 
    
69. The Unix column assumes that you are not accessing a serial line (like a tty) in canonical mode. If you are, then CR on input becomes ``\n'', and ``\n'' on output becomes CRLF.
    
70. 
    
71. These are just the most common definitions of \n and \r in Perl. There may well be others. For example, on an EBCDIC implementation such as z/OS (OS/390) or OS/400 (using the ILE, the PASE is ASCII-based) the above material is similar to ``Unix'' but the code numbers change:
    
72. 
    
73.     LF  eq  \025  eq  \x15  eq  \cU  eq  chr(21)  eq  CP-1047 21
    
74.     LF  eq  \045  eq  \x25  eq           chr(37)  eq  CP-0037 37
    
75.     CR  eq  \015  eq  \x0D  eq  \cM  eq  chr(13)  eq  CP-1047 13
    
76.     CR  eq  \015  eq  \x0D  eq  \cM  eq  chr(13)  eq  CP-0037 13
    
77. 
    
78.              | z/OS | OS/400 |
    
79.         ----------------------
    
80.         \n   |  LF  |  LF    |
    
81.         \r   |  CR  |  CR    |
    
82.         \n * |  LF  |  LF    |
    
83.         \r * |  CR  |  CR    |
    
84.         ----------------------
    
85.         * text-mode STDIO

復(fù)制代碼