Proxy Error 400 Putty
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the remote server returned an error (400) bad request. c# the company Business Learn more about hiring developers or posting ads with us Stack remote server returned error 400 bad request Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community
The Remote Server Returned An Error 400 Bad Request Httpwebrequest
of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up black screen and error 400 bad request up vote 1 down vote favorite I was trying telnet
Http Error 400 Bad Request
into a Web server and send a multiline request message. I have to include in the request message the If-modified-since. I made settings for Win7. For instance when I type telnet edition.cnn.com 80 on my command prompt, it opens a black empty screen, I don't see any thing that I type. Then I wrote this line on the black screen GET pageName HTTP/1.0, it returned 400 Bad Request Error and says connection the remote server returned an error (400) bad request. wcf closed. What should I do? I used get pagename for an example. telnet apache share|improve this question edited Nov 4 '12 at 11:31 Filip Roséen - refp 39.5k1188154 asked Nov 4 '12 at 11:28 Ahmet Tanakol 4091427 1 The Windows telnet client is notoriously bad. Try again with something like PuTTY. –Some programmer dude Nov 4 '12 at 11:33 ok I finally get the content by typing just for a page GET /21838937.asp now I have to include If-modified-since –Ahmet Tanakol Nov 4 '12 at 11:48 add a comment| 3 Answers 3 active oldest votes up vote 3 down vote accepted If you want to use e.g. a telnet client to manually get web-pages, you have to remember the format of a HTTP request header: GET pageName HTTP/1.0 additional header additional header Note that the last line is an empty line. You might also need HTTP/1.1 for certain headers to make sense. Please read a HTTP specification for more information and what headers are standard. The "black screen" is simply the telnet program running in a command window. share|improve this answer edited Mar 22 at 17:04 answered Nov 4 '12 at 11:56 Some programmer dude 212k16146255 and what about the blank screen op is mentioning ? –Vamsi Pav
protocol completely. So the Web server was unable to understand the request and process it. It almost always means bad programming of the client system and/or the Web
The Remote Server Returned An Error 400 Bad Request At System Net Httpwebrequest Getresponse
server. Fixing 400 errors - general There is a low-level problem in the client the remote server returned an error (400) bad request outlook or the Web server or both. 95% of the time this is because of a problem on the client system 400 bad request fix e.g. there is something unstable on your PC running the Web browser. Is your PC secure ?. If your PC is not well-protected, then all kinds of problems may occur - including HTTP 400 http://stackoverflow.com/questions/13218126/black-screen-and-error-400-bad-request errors. If you run Windows, stay uptodate with automatic security updates from Microsoft and possibly consider getting a registry cleaner. Always have good anti-virus and spyware protection. Invest in a hardware firewall if you can afford one. Be sensible surfing the Web - block pop-up windows and avoid bad sites. If your PC security is compromised, then Web traffic out from your PC to the Internet may be secretly http://www.checkupdown.com/status/E400.html corrupted by malware (spyware, viruses, etc.) running on your PC. This can be difficult for you to detect. Have you installed web-based software ?. Some social networking and games sites ask you to download and run software on your PC so you can interact with other people on the Internet directly (without using your Web browser). This software, if badly written or even criminal, can corrupt all HTTP traffic from your PC. Getting rid of that defective software can be difficult. At worst you may have to reinstall your operating system again (possibly losing all your personal data on your PC if you do not have backup). How stable is your Internet connection ?. If you have recently changed ISPs or your ISP is very slow or unreliable, then Web traffic from your PC out to any site on the Internet may be corrupt. Your ISP may have reconfigured some of their setup (e.g. introduced new proxy servers or cacheing) that is causing some instability. A possible sign of problems here is if you can not easily browse the Web site of your ISP. You can also try to check that the Web site you are actually visiting is the one you t
corporate jobs find themselves behind a firewall which only allows outgoing traffic to destination ports 21 (ftp), 80 (http) and 443 (https). To access one's network at home, the workaround is to run the SSH server at home on port 443 http://home.icequake.net/~nemesis/blog/index.php/archives/283 instead of the usual port 22, then use the SSH client to create a tunnel so that arbitrary traffic will be sent through your home machine instead of through the firewall. Some people who are even unluckier find themselves behind a firewall which does layer 7 packet inspection, meaning that traffic outgoing to a destination port of 443 that does not look like HTTPS traffic will be dropped by the firewall. Fortunately, PuTTY combined with proxytunnel will allow the passing of bad request non-HTTPS traffic through this type of firewall. It is accomplished through a "triple-proxy" method, where a connection is made to your HTTPS proxy web server at home through your restrictive corporate proxy, then an SSH session is tunneled through the HTTPS connection, and then the SSH connection acts as a proxy for the network traffic that is not permitted to pass through the corporate network. All traffic is encrypted and completely unidentifiable by packet inspection as anything other than a normal remote server returned encrypted HTTPS session. You must configure an Apache web server at home to listen with HTTPS on port 443, and also enable mod_proxy to accept HTTP proxy commands within the encrypted HTTPS session. (You must restrict the proxy commands to only certain username/password combinations, or alternatively restrict them to connections initiated from the external IP address of your corporate network. Failing to do this will allow any malicious user on the Internet to pretend that your server is doing the bad things that they are up to.) This document explains how to do the complex configuration, and so does this other document, but there will be at least two problems. One is due to an error in the document. The command for proxytunnel must be of the following form: c:\proxytunnel\proxytunnel.exe -X -q -p workproxy:3128 -r my.home.webserver.net:443 -d %host:%port -H "User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Win32)"\n -- special care must be taken to place the "\n" newline AFTER the quoted User-Agent, not within the quotes. Two is due to the reluctance of Apache developers to accept a bug fix for the behavior of mod_proxy when an HTTPS connection is proxied. You will have to download the patch in the bug tracker, apply it to an Apache source tree, and compile your own Apache. Once you have done both of these things, and configured both the proxy and SSH tunnel settings in PuTTY, then enter the INTERNAL name of a chosen machine