400 Error Tomcat
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 company Business Learn more about hiring developers or posting ads with http 400 error us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow tomcat 500 error Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up
Tomcat 404 Error
Tomcat 6.0.36 not reporting why it responded with 400 up vote 8 down vote favorite 3 I have a tomcat server and java client with java.net.HttpUrlConnection sending messages. Usually all works fine, but there some requests the client sends out which are
Tomcat 403 Error
responded with a 400 http error. The problem is that nothing is shown on tomcat logs. I even tried to put .level=fine and other log level changes, and still no exception or error was shown. I'm suspecting bad encoding in request or something like that, but tomcat doesn't give me any clues. By the way, the URL is OK. I also see the request reaches the server but not to my servlet. It appears tomcat gets the message, declares it bad and doesn't log what's 404 error in tomcat 7 wrong. Can anybody think of a way to see the 400 reason? Thank you java tomcat share|improve this question edited Sep 13 '13 at 12:38 asked Sep 12 '13 at 21:02 user967710 80611531 What log files did you look at? Do you have a Web server like Apache in front on Tomcat? –David Levesque Sep 12 '13 at 21:27 No. I don't. I looked at Catalina.out, localhost... –user967710 Sep 13 '13 at 6:04 Tell us more about your logging mechanism. Also tell us which kind of application are you using? Spring/plain servlet ... ?? –Ashay Thorat Sep 13 '13 at 12:45 Plain servlet. I see in debug time that the server doesn't get the message. Tomcat blocks it. –user967710 Sep 14 '13 at 20:13 What is in the response body when you get the 400 status code? –Henry Sep 15 '13 at 6:46 | show 3 more comments 2 Answers 2 active oldest votes up vote 14 down vote accepted I finally figured out - I saw that the size of the total headers + size of data written to OutputStream - was exceptionally high - and so I defined in the Tomcat HTTP connector: Connector port="8080" protocol="HTTP 1/1" maxPostSize="10485760" maxHttpHeaderSize="10485760"/ It is a shame Tomcat doesn't just tell me this, and I had to guess my - I will report this as a bug. Thank you share|improve this answer answered Sep 16 '13 at 8:58 user967710 80611531 2 it
here for a quick overview of the site Help Center Detailed
404 Error In Tomcat Eclipse
answers to any questions you might have Meta Discuss the permgen error tomcat workings and policies of this site About Us Learn more about Stack Overflow the tomcat outofmemoryerror company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join http://stackoverflow.com/questions/18774285/tomcat-6-0-36-not-reporting-why-it-responded-with-400 the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Plain text 400 error message in struts2 + Tomcat up vote 0 down vote favorite I want an action to issue http://stackoverflow.com/questions/5366159/plain-text-400-error-message-in-struts2-tomcat a 400 error HTTP response with an explanation of the problem in text/plain whenever a validation fails. I can use org.apache.struts2.dispatcher.HttpHeaderResult to get the 400 error: @Action(results = { @Result(name = SUCCESS, type=ResultTypes.HTTP_HEADER, params = { "status", "200" }), @Result(name = INPUT, type=ResultTypes.HTTP_HEADER, params = { "error", "400", "errorMessage", "${errorMessage}" }) }) @Override public String execute() { return INPUT; } public String getErrorMessage() { return "There was an error"; } The problem is that Tomcat "wraps" my response into an HTML page as follows: HTTP/1.1 400 Bad Request Server: Apache-Coyote/1.1 Content-Type: text/html;charset=utf-8 Content-Length: 1214 Date: Sun, 20 Mar 2011 00:43:55 GMT Connection: close
HTTP Status 400 - There was an error
type Statu
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss http://serverfault.com/questions/481259/tomcat-always-returns-status-code-400 the workings and policies of this site About Us Learn more https://web.liferay.com/community/forums/-/message_boards/message/94207 about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign 404 error up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Tomcat always returns status code 400 up vote 1 down vote favorite 1 I've just installed Tomcat on CentOS 6.3. # yum install tomcat6 # service tomcat6 start According to the tutorials I've looked at, 404 error in I should be able to see a test page now. # curl -I 127.0.0.1:8080 HTTP/1.1 400 Bad Request ... # curl -I 127.0.0.1:8080/manager/html HTTP/1.1 400 Bad Request ... Why am I getting 400 here? Is there something else that I need to configure? centos tomcat tomcat6 share|improve this question asked Feb 21 '13 at 20:32 Dean 12816 add a comment| 2 Answers 2 active oldest votes up vote 4 down vote accepted Tomcat always returns status code 400 Because the webapps directory is empty: # ls -l /usr/share/tomcat6/webapps/ total 0 https://issues.apache.org/bugzilla/show_bug.cgi?id=50734 Either create a dummy ROOT context to get a 404 status: # mkdir /usr/share/tomcat6/webapps/ROOT # ls -l /usr/share/tomcat6/webapps/ total 4 drwxr-xr-x 2 root root 4096 Feb 22 07:47 ROOT # service tomcat6 restart Stopping tomcat6: [ OK ] Starting tomcat6: [ OK ] # curl -I localhost:8080 HTTP/1.1 404 Not Found Server: Apache-Coyote/1.1 Content-Type: text/html;charset=utf-8 Content-Length: 955 Date: Fri, 22 Feb 2013 06:48:06 GMT or... install the tomcat6-webapps package to get a 200: yum info tomcat6-webapps Name : tomcat6-webapps Arch : noarch Version
Search Forums Home » Liferay Portal » English » Liferay Legacy Recent Posts Statistics RSS (Opens New Window) Answer (Unmark) Mark as an Answer Threads [ Previous | Next ] Problem with deployment - HTTP 400 error Anonymous December 13, 2006 6:21 AM RE: Problem with deployment - HTTP 400 error Elisabeth VanSchaardenburg December 13, 2006 7:30 AM RE: Problem with deployment - HTTP 400 error Anonymous December 13, 2006 8:30 AM RE: Problem with deployment - HTTP 400 error Elisabeth VanSchaardenburg December 13, 2006 9:01 AM RE: Problem with deployment - HTTP 400 error rk p December 13, 2006 9:05 AM RE: Problem with deployment - HTTP 400 error Chad Shryock December 13, 2006 1:40 PM RE: Problem with deployment - HTTP 400 error Elisabeth VanSchaardenburg December 13, 2006 4:41 PM RE: Problem with deployment - HTTP 400 error rk p December 13, 2006 11:02 PM RE: Problem with deployment - HTTP 400 error rk p December 13, 2006 11:08 PM Problem with deployment - HTTP 400 error December 13, 2006 6:21 AM Answer Anonymous I'm a newbie to portal development and I am currently trying to migrate to liferay 4.2. I managed to successfully deploy my application wars in liferay 4.2 with tomcat, but when I try to access http://localhost:8000 (I had changed the non-SSL Connector port in server.xml to 8000 from the default 8080) I get a HTTP:400 Bad requesterror in IE. Can anyone plz suggest what might cause this problem? I've been desperately trying to resolve this. Any help would be greatly appreciated. Sign in to vote. Flag Please sign in to flag this as inappropriate. RE: Problem with deployment - HTTP 400 error December 13, 2006 7:30 AM Answer Elisabeth VanSchaardenburg Rank: Regular Member Posts: 184 Join Date: May 23, 2006 Recent Posts I'd suggest looking at your Tomcat log files and make sure everything started successfully. You should see some stuff like this: Loading jar:file:/D:/3-Projects/400/tomcat/webapps/ROOT/WEB-INF/lib/portal-ejb.jar!/system.propertiesLoading jar:file:/D:/3-Projects/400/tomcat/webapps/ROOT/WEB-INF/lib/portal-ejb.jar!/portal.propertiesLoading file:/D:/3-Projects/400/tomcat/weba