Manual HTTP(S) request
up vote
9
down vote
favorite
I am looking for a tool (possibly on Linux) that will allow me to make a manual HTTP or HTTPS request. By manual, I really mean it: I should be able to feed it a text file which looks like
POST /foo HTTP/1.1
Host: www.example.com
Accept: text/xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-gb,en;q=0.5
Content-Type: text/plain
Content-Length: 11
Hello world
and a destination URL (www.example.com/foo), and send the request to the URL. At most, it would be useful if the Content_Length header was automatically computed.
I would be able to write such a tool using some library like httplib in Python, but the very reason I need it is to do manual investigation when something goes wrong with such libraries.
linux http https
add a comment |
up vote
9
down vote
favorite
I am looking for a tool (possibly on Linux) that will allow me to make a manual HTTP or HTTPS request. By manual, I really mean it: I should be able to feed it a text file which looks like
POST /foo HTTP/1.1
Host: www.example.com
Accept: text/xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-gb,en;q=0.5
Content-Type: text/plain
Content-Length: 11
Hello world
and a destination URL (www.example.com/foo), and send the request to the URL. At most, it would be useful if the Content_Length header was automatically computed.
I would be able to write such a tool using some library like httplib in Python, but the very reason I need it is to do manual investigation when something goes wrong with such libraries.
linux http https
1
https specific question: superuser.com/questions/346958/…
– Ciro Santilli 新疆改造中心 六四事件 法轮功
Oct 5 at 9:34
add a comment |
up vote
9
down vote
favorite
up vote
9
down vote
favorite
I am looking for a tool (possibly on Linux) that will allow me to make a manual HTTP or HTTPS request. By manual, I really mean it: I should be able to feed it a text file which looks like
POST /foo HTTP/1.1
Host: www.example.com
Accept: text/xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-gb,en;q=0.5
Content-Type: text/plain
Content-Length: 11
Hello world
and a destination URL (www.example.com/foo), and send the request to the URL. At most, it would be useful if the Content_Length header was automatically computed.
I would be able to write such a tool using some library like httplib in Python, but the very reason I need it is to do manual investigation when something goes wrong with such libraries.
linux http https
I am looking for a tool (possibly on Linux) that will allow me to make a manual HTTP or HTTPS request. By manual, I really mean it: I should be able to feed it a text file which looks like
POST /foo HTTP/1.1
Host: www.example.com
Accept: text/xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-gb,en;q=0.5
Content-Type: text/plain
Content-Length: 11
Hello world
and a destination URL (www.example.com/foo), and send the request to the URL. At most, it would be useful if the Content_Length header was automatically computed.
I would be able to write such a tool using some library like httplib in Python, but the very reason I need it is to do manual investigation when something goes wrong with such libraries.
linux http https
linux http https
asked Jul 18 '11 at 20:32
Andrea
435157
435157
1
https specific question: superuser.com/questions/346958/…
– Ciro Santilli 新疆改造中心 六四事件 法轮功
Oct 5 at 9:34
add a comment |
1
https specific question: superuser.com/questions/346958/…
– Ciro Santilli 新疆改造中心 六四事件 法轮功
Oct 5 at 9:34
1
1
https specific question: superuser.com/questions/346958/…
– Ciro Santilli 新疆改造中心 六四事件 法轮功
Oct 5 at 9:34
https specific question: superuser.com/questions/346958/…
– Ciro Santilli 新疆改造中心 六四事件 法轮功
Oct 5 at 9:34
add a comment |
5 Answers
5
active
oldest
votes
up vote
9
down vote
accepted
wget has a --post-file option which should work for you.
Edit: Also, there's Ncat, which you would use in a similar fashion to Randolf Richardson's telnet suggestion, except that it also supports SSL/HTTPS:
ncat -C --ssl www.example.com 443 < input.txt > output.txt
5
If you need HTTPS, use openssl instead of netcat: openssl s_client -connect <address>:443
– Ambroz Bizjak
Jul 18 '11 at 22:24
wget --post-file will add headers and use the specified file only for the body of the request.
– David Balažic
Apr 3 at 18:16
add a comment |
up vote
6
down vote
For HTTP (not HTTPS), one alternative to the "wget" command that comes to mind is to use telnet as follows:
- telnet hostname 80 < input.txt > output.txt
The file "input.txt" is your list of pre-set commands that you wish to feed to the host at hostname and the file "output.txt" will store the response.
1
This made me wonder if netcat supports SSL, and lo-and-behold, there's Ncat, an SSL-enabled netcat clone.
– Chris Acheson
Jul 18 '11 at 22:15
@Chris Acheson (+1): That's fantastic! Please feel free to copy what I wrote in a separate answer and adapt it to a solution that utilizes NetCat (I'll vote for your answer if you do this).
– Randolf Richardson
Jul 18 '11 at 22:38
add a comment |
up vote
1
down vote
You can issue a GET request with OpenSSL:
openssl s_client -quiet -connect cdn.sstatic.net:443 <<eof
GET /stackexchange/js/universal-login.js HTTP/1.1
Connection: close
Host: cdn.sstatic.net
eof
Note that you can also use "HTTP/2", but be careful because some servers
(e.g. github.com) do not support it.
add a comment |
up vote
0
down vote
For me, it worked creating a request file (Example: request.txt
)
POST /foo HTTP/1.1
Host: www.example.com
Accept: text/xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-gb,en;q=0.5
Content-Type: text/plain; charset=utf-8
Content-Length: 11
Connection: close
Hello world
And then call the openssl s_client
command:
cat request.txt | openssl s_client -quiet -connect www.example.com:443
However, be careful about some points:
- The file must be encoded properly, specially the content body. Better if you include a header
Content-type: text/plain; charset=utf-8
if the file is utf-8 encoded. - The line endings for the headers must be CR/LF. Only with LF the web server could return
HTTP/1.1 505 HTTP Version Not Supported
, because the standard HTTP protocol uses CR/LF for line endings (https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html). You can use theunix2dos
command to do this conversion. - Add a
Connection: close
header to terminate the request and return from the call. Otherwise, the command will be awaiting for user interaction, if the server normally responds with aConnection: keep-alive
header.
New contributor
add a comment |
up vote
-1
down vote
I'm surprised no one mentioned cURL. It is made exactly for what you want to do. And it is available on practically any platform (including Windows).
So for your example all you would do is:
curl -H 'Content-Type: text/plain' -d 'Hello World' www.example.com
Which captured from Wireshark will net you:
POST / HTTP/1.1
User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15
Host: www.example.com
Accept: */*
Content-Type: text/plain
Content-Length: 11
Hello world
You can easily modify the headers further if you wish to do all kinds of stuff (i.e. change the user-agent, etc).
Edit: Didn't notice the "from a file" requirement. You can do that too, either plain ascii or binary files. You just specify the filename with an @ symbol
-d @/tmp/HelloWorldFile
curl is almost what I want, but requires me to specify the headers on the command line, which is very impractical. I need something which allows me to specify the complete text of the request, including the method and the headers, from a file, and ncat does eaxctly what I want. Thank you anyway :-)
– Andrea
Jul 21 '11 at 9:05
add a comment |
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
9
down vote
accepted
wget has a --post-file option which should work for you.
Edit: Also, there's Ncat, which you would use in a similar fashion to Randolf Richardson's telnet suggestion, except that it also supports SSL/HTTPS:
ncat -C --ssl www.example.com 443 < input.txt > output.txt
5
If you need HTTPS, use openssl instead of netcat: openssl s_client -connect <address>:443
– Ambroz Bizjak
Jul 18 '11 at 22:24
wget --post-file will add headers and use the specified file only for the body of the request.
– David Balažic
Apr 3 at 18:16
add a comment |
up vote
9
down vote
accepted
wget has a --post-file option which should work for you.
Edit: Also, there's Ncat, which you would use in a similar fashion to Randolf Richardson's telnet suggestion, except that it also supports SSL/HTTPS:
ncat -C --ssl www.example.com 443 < input.txt > output.txt
5
If you need HTTPS, use openssl instead of netcat: openssl s_client -connect <address>:443
– Ambroz Bizjak
Jul 18 '11 at 22:24
wget --post-file will add headers and use the specified file only for the body of the request.
– David Balažic
Apr 3 at 18:16
add a comment |
up vote
9
down vote
accepted
up vote
9
down vote
accepted
wget has a --post-file option which should work for you.
Edit: Also, there's Ncat, which you would use in a similar fashion to Randolf Richardson's telnet suggestion, except that it also supports SSL/HTTPS:
ncat -C --ssl www.example.com 443 < input.txt > output.txt
wget has a --post-file option which should work for you.
Edit: Also, there's Ncat, which you would use in a similar fashion to Randolf Richardson's telnet suggestion, except that it also supports SSL/HTTPS:
ncat -C --ssl www.example.com 443 < input.txt > output.txt
edited Jul 19 '11 at 4:15
answered Jul 18 '11 at 20:42
Chris Acheson
94976
94976
5
If you need HTTPS, use openssl instead of netcat: openssl s_client -connect <address>:443
– Ambroz Bizjak
Jul 18 '11 at 22:24
wget --post-file will add headers and use the specified file only for the body of the request.
– David Balažic
Apr 3 at 18:16
add a comment |
5
If you need HTTPS, use openssl instead of netcat: openssl s_client -connect <address>:443
– Ambroz Bizjak
Jul 18 '11 at 22:24
wget --post-file will add headers and use the specified file only for the body of the request.
– David Balažic
Apr 3 at 18:16
5
5
If you need HTTPS, use openssl instead of netcat: openssl s_client -connect <address>:443
– Ambroz Bizjak
Jul 18 '11 at 22:24
If you need HTTPS, use openssl instead of netcat: openssl s_client -connect <address>:443
– Ambroz Bizjak
Jul 18 '11 at 22:24
wget --post-file will add headers and use the specified file only for the body of the request.
– David Balažic
Apr 3 at 18:16
wget --post-file will add headers and use the specified file only for the body of the request.
– David Balažic
Apr 3 at 18:16
add a comment |
up vote
6
down vote
For HTTP (not HTTPS), one alternative to the "wget" command that comes to mind is to use telnet as follows:
- telnet hostname 80 < input.txt > output.txt
The file "input.txt" is your list of pre-set commands that you wish to feed to the host at hostname and the file "output.txt" will store the response.
1
This made me wonder if netcat supports SSL, and lo-and-behold, there's Ncat, an SSL-enabled netcat clone.
– Chris Acheson
Jul 18 '11 at 22:15
@Chris Acheson (+1): That's fantastic! Please feel free to copy what I wrote in a separate answer and adapt it to a solution that utilizes NetCat (I'll vote for your answer if you do this).
– Randolf Richardson
Jul 18 '11 at 22:38
add a comment |
up vote
6
down vote
For HTTP (not HTTPS), one alternative to the "wget" command that comes to mind is to use telnet as follows:
- telnet hostname 80 < input.txt > output.txt
The file "input.txt" is your list of pre-set commands that you wish to feed to the host at hostname and the file "output.txt" will store the response.
1
This made me wonder if netcat supports SSL, and lo-and-behold, there's Ncat, an SSL-enabled netcat clone.
– Chris Acheson
Jul 18 '11 at 22:15
@Chris Acheson (+1): That's fantastic! Please feel free to copy what I wrote in a separate answer and adapt it to a solution that utilizes NetCat (I'll vote for your answer if you do this).
– Randolf Richardson
Jul 18 '11 at 22:38
add a comment |
up vote
6
down vote
up vote
6
down vote
For HTTP (not HTTPS), one alternative to the "wget" command that comes to mind is to use telnet as follows:
- telnet hostname 80 < input.txt > output.txt
The file "input.txt" is your list of pre-set commands that you wish to feed to the host at hostname and the file "output.txt" will store the response.
For HTTP (not HTTPS), one alternative to the "wget" command that comes to mind is to use telnet as follows:
- telnet hostname 80 < input.txt > output.txt
The file "input.txt" is your list of pre-set commands that you wish to feed to the host at hostname and the file "output.txt" will store the response.
answered Jul 18 '11 at 20:54
Randolf Richardson
13.4k2850
13.4k2850
1
This made me wonder if netcat supports SSL, and lo-and-behold, there's Ncat, an SSL-enabled netcat clone.
– Chris Acheson
Jul 18 '11 at 22:15
@Chris Acheson (+1): That's fantastic! Please feel free to copy what I wrote in a separate answer and adapt it to a solution that utilizes NetCat (I'll vote for your answer if you do this).
– Randolf Richardson
Jul 18 '11 at 22:38
add a comment |
1
This made me wonder if netcat supports SSL, and lo-and-behold, there's Ncat, an SSL-enabled netcat clone.
– Chris Acheson
Jul 18 '11 at 22:15
@Chris Acheson (+1): That's fantastic! Please feel free to copy what I wrote in a separate answer and adapt it to a solution that utilizes NetCat (I'll vote for your answer if you do this).
– Randolf Richardson
Jul 18 '11 at 22:38
1
1
This made me wonder if netcat supports SSL, and lo-and-behold, there's Ncat, an SSL-enabled netcat clone.
– Chris Acheson
Jul 18 '11 at 22:15
This made me wonder if netcat supports SSL, and lo-and-behold, there's Ncat, an SSL-enabled netcat clone.
– Chris Acheson
Jul 18 '11 at 22:15
@Chris Acheson (+1): That's fantastic! Please feel free to copy what I wrote in a separate answer and adapt it to a solution that utilizes NetCat (I'll vote for your answer if you do this).
– Randolf Richardson
Jul 18 '11 at 22:38
@Chris Acheson (+1): That's fantastic! Please feel free to copy what I wrote in a separate answer and adapt it to a solution that utilizes NetCat (I'll vote for your answer if you do this).
– Randolf Richardson
Jul 18 '11 at 22:38
add a comment |
up vote
1
down vote
You can issue a GET request with OpenSSL:
openssl s_client -quiet -connect cdn.sstatic.net:443 <<eof
GET /stackexchange/js/universal-login.js HTTP/1.1
Connection: close
Host: cdn.sstatic.net
eof
Note that you can also use "HTTP/2", but be careful because some servers
(e.g. github.com) do not support it.
add a comment |
up vote
1
down vote
You can issue a GET request with OpenSSL:
openssl s_client -quiet -connect cdn.sstatic.net:443 <<eof
GET /stackexchange/js/universal-login.js HTTP/1.1
Connection: close
Host: cdn.sstatic.net
eof
Note that you can also use "HTTP/2", but be careful because some servers
(e.g. github.com) do not support it.
add a comment |
up vote
1
down vote
up vote
1
down vote
You can issue a GET request with OpenSSL:
openssl s_client -quiet -connect cdn.sstatic.net:443 <<eof
GET /stackexchange/js/universal-login.js HTTP/1.1
Connection: close
Host: cdn.sstatic.net
eof
Note that you can also use "HTTP/2", but be careful because some servers
(e.g. github.com) do not support it.
You can issue a GET request with OpenSSL:
openssl s_client -quiet -connect cdn.sstatic.net:443 <<eof
GET /stackexchange/js/universal-login.js HTTP/1.1
Connection: close
Host: cdn.sstatic.net
eof
Note that you can also use "HTTP/2", but be careful because some servers
(e.g. github.com) do not support it.
edited Dec 1 at 19:38
answered Jan 22 at 5:04
Steven Penny
4,1101683133
4,1101683133
add a comment |
add a comment |
up vote
0
down vote
For me, it worked creating a request file (Example: request.txt
)
POST /foo HTTP/1.1
Host: www.example.com
Accept: text/xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-gb,en;q=0.5
Content-Type: text/plain; charset=utf-8
Content-Length: 11
Connection: close
Hello world
And then call the openssl s_client
command:
cat request.txt | openssl s_client -quiet -connect www.example.com:443
However, be careful about some points:
- The file must be encoded properly, specially the content body. Better if you include a header
Content-type: text/plain; charset=utf-8
if the file is utf-8 encoded. - The line endings for the headers must be CR/LF. Only with LF the web server could return
HTTP/1.1 505 HTTP Version Not Supported
, because the standard HTTP protocol uses CR/LF for line endings (https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html). You can use theunix2dos
command to do this conversion. - Add a
Connection: close
header to terminate the request and return from the call. Otherwise, the command will be awaiting for user interaction, if the server normally responds with aConnection: keep-alive
header.
New contributor
add a comment |
up vote
0
down vote
For me, it worked creating a request file (Example: request.txt
)
POST /foo HTTP/1.1
Host: www.example.com
Accept: text/xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-gb,en;q=0.5
Content-Type: text/plain; charset=utf-8
Content-Length: 11
Connection: close
Hello world
And then call the openssl s_client
command:
cat request.txt | openssl s_client -quiet -connect www.example.com:443
However, be careful about some points:
- The file must be encoded properly, specially the content body. Better if you include a header
Content-type: text/plain; charset=utf-8
if the file is utf-8 encoded. - The line endings for the headers must be CR/LF. Only with LF the web server could return
HTTP/1.1 505 HTTP Version Not Supported
, because the standard HTTP protocol uses CR/LF for line endings (https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html). You can use theunix2dos
command to do this conversion. - Add a
Connection: close
header to terminate the request and return from the call. Otherwise, the command will be awaiting for user interaction, if the server normally responds with aConnection: keep-alive
header.
New contributor
add a comment |
up vote
0
down vote
up vote
0
down vote
For me, it worked creating a request file (Example: request.txt
)
POST /foo HTTP/1.1
Host: www.example.com
Accept: text/xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-gb,en;q=0.5
Content-Type: text/plain; charset=utf-8
Content-Length: 11
Connection: close
Hello world
And then call the openssl s_client
command:
cat request.txt | openssl s_client -quiet -connect www.example.com:443
However, be careful about some points:
- The file must be encoded properly, specially the content body. Better if you include a header
Content-type: text/plain; charset=utf-8
if the file is utf-8 encoded. - The line endings for the headers must be CR/LF. Only with LF the web server could return
HTTP/1.1 505 HTTP Version Not Supported
, because the standard HTTP protocol uses CR/LF for line endings (https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html). You can use theunix2dos
command to do this conversion. - Add a
Connection: close
header to terminate the request and return from the call. Otherwise, the command will be awaiting for user interaction, if the server normally responds with aConnection: keep-alive
header.
New contributor
For me, it worked creating a request file (Example: request.txt
)
POST /foo HTTP/1.1
Host: www.example.com
Accept: text/xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-gb,en;q=0.5
Content-Type: text/plain; charset=utf-8
Content-Length: 11
Connection: close
Hello world
And then call the openssl s_client
command:
cat request.txt | openssl s_client -quiet -connect www.example.com:443
However, be careful about some points:
- The file must be encoded properly, specially the content body. Better if you include a header
Content-type: text/plain; charset=utf-8
if the file is utf-8 encoded. - The line endings for the headers must be CR/LF. Only with LF the web server could return
HTTP/1.1 505 HTTP Version Not Supported
, because the standard HTTP protocol uses CR/LF for line endings (https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html). You can use theunix2dos
command to do this conversion. - Add a
Connection: close
header to terminate the request and return from the call. Otherwise, the command will be awaiting for user interaction, if the server normally responds with aConnection: keep-alive
header.
New contributor
New contributor
answered 21 hours ago
F.Igor
1011
1011
New contributor
New contributor
add a comment |
add a comment |
up vote
-1
down vote
I'm surprised no one mentioned cURL. It is made exactly for what you want to do. And it is available on practically any platform (including Windows).
So for your example all you would do is:
curl -H 'Content-Type: text/plain' -d 'Hello World' www.example.com
Which captured from Wireshark will net you:
POST / HTTP/1.1
User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15
Host: www.example.com
Accept: */*
Content-Type: text/plain
Content-Length: 11
Hello world
You can easily modify the headers further if you wish to do all kinds of stuff (i.e. change the user-agent, etc).
Edit: Didn't notice the "from a file" requirement. You can do that too, either plain ascii or binary files. You just specify the filename with an @ symbol
-d @/tmp/HelloWorldFile
curl is almost what I want, but requires me to specify the headers on the command line, which is very impractical. I need something which allows me to specify the complete text of the request, including the method and the headers, from a file, and ncat does eaxctly what I want. Thank you anyway :-)
– Andrea
Jul 21 '11 at 9:05
add a comment |
up vote
-1
down vote
I'm surprised no one mentioned cURL. It is made exactly for what you want to do. And it is available on practically any platform (including Windows).
So for your example all you would do is:
curl -H 'Content-Type: text/plain' -d 'Hello World' www.example.com
Which captured from Wireshark will net you:
POST / HTTP/1.1
User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15
Host: www.example.com
Accept: */*
Content-Type: text/plain
Content-Length: 11
Hello world
You can easily modify the headers further if you wish to do all kinds of stuff (i.e. change the user-agent, etc).
Edit: Didn't notice the "from a file" requirement. You can do that too, either plain ascii or binary files. You just specify the filename with an @ symbol
-d @/tmp/HelloWorldFile
curl is almost what I want, but requires me to specify the headers on the command line, which is very impractical. I need something which allows me to specify the complete text of the request, including the method and the headers, from a file, and ncat does eaxctly what I want. Thank you anyway :-)
– Andrea
Jul 21 '11 at 9:05
add a comment |
up vote
-1
down vote
up vote
-1
down vote
I'm surprised no one mentioned cURL. It is made exactly for what you want to do. And it is available on practically any platform (including Windows).
So for your example all you would do is:
curl -H 'Content-Type: text/plain' -d 'Hello World' www.example.com
Which captured from Wireshark will net you:
POST / HTTP/1.1
User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15
Host: www.example.com
Accept: */*
Content-Type: text/plain
Content-Length: 11
Hello world
You can easily modify the headers further if you wish to do all kinds of stuff (i.e. change the user-agent, etc).
Edit: Didn't notice the "from a file" requirement. You can do that too, either plain ascii or binary files. You just specify the filename with an @ symbol
-d @/tmp/HelloWorldFile
I'm surprised no one mentioned cURL. It is made exactly for what you want to do. And it is available on practically any platform (including Windows).
So for your example all you would do is:
curl -H 'Content-Type: text/plain' -d 'Hello World' www.example.com
Which captured from Wireshark will net you:
POST / HTTP/1.1
User-Agent: curl/7.19.7 (x86_64-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15
Host: www.example.com
Accept: */*
Content-Type: text/plain
Content-Length: 11
Hello world
You can easily modify the headers further if you wish to do all kinds of stuff (i.e. change the user-agent, etc).
Edit: Didn't notice the "from a file" requirement. You can do that too, either plain ascii or binary files. You just specify the filename with an @ symbol
-d @/tmp/HelloWorldFile
edited Jul 20 '11 at 20:57
answered Jul 20 '11 at 20:46
Nicholi
593411
593411
curl is almost what I want, but requires me to specify the headers on the command line, which is very impractical. I need something which allows me to specify the complete text of the request, including the method and the headers, from a file, and ncat does eaxctly what I want. Thank you anyway :-)
– Andrea
Jul 21 '11 at 9:05
add a comment |
curl is almost what I want, but requires me to specify the headers on the command line, which is very impractical. I need something which allows me to specify the complete text of the request, including the method and the headers, from a file, and ncat does eaxctly what I want. Thank you anyway :-)
– Andrea
Jul 21 '11 at 9:05
curl is almost what I want, but requires me to specify the headers on the command line, which is very impractical. I need something which allows me to specify the complete text of the request, including the method and the headers, from a file, and ncat does eaxctly what I want. Thank you anyway :-)
– Andrea
Jul 21 '11 at 9:05
curl is almost what I want, but requires me to specify the headers on the command line, which is very impractical. I need something which allows me to specify the complete text of the request, including the method and the headers, from a file, and ncat does eaxctly what I want. Thank you anyway :-)
– Andrea
Jul 21 '11 at 9:05
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f312094%2fmanual-https-request%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
https specific question: superuser.com/questions/346958/…
– Ciro Santilli 新疆改造中心 六四事件 法轮功
Oct 5 at 9:34