Forum Discussion
Willy_82807
Oct 05, 2010Nimbostratus
Fileupload problem
I am new to BigIP. I am load balancing two servers both running java servlet / jsp applications. Some of the 3rd party modules are hosted in iframes and to get the content it uses a non relative url. The application as a whole needs to use https. So I created this irule.
when HTTP_REQUEST {
HTTP::redirect https://[HTTP::host][HTTP::uri]
}
But now I am getting the unintended consequence that fileuploads are working sometimes and not other times. It is not a file size issue. It happens in Firefox and IE8. This is the error message I am getting.HTTP Status 501 - Method 240776-- GET is not defined in RFC 2068 and is not supported by the Servlet API
type Status report
messageMethod 240776-- GET is not defined in RFC 2068 and is not supported by the Servlet API
descriptionThe server does not support the functionality needed to fulfill this request (Method 240776-- GET is not defined in RFC 2068 and is not supported by the Servlet API ).
Apache Tomcat/5.5.29
When I go directly to the Tomcat server (skip the load balancer) and upload the same file I do not get an error and it uploads quickly. This does not happen for every file. But I have not yet noticed the common denominator in the files that is causing the issue. Most files upload fine. I do have one that consistently throws this error that is useful for debugging.
These applications ran for a while before the BigIP appliance was installed and never had this issue. So I am concerned that the problem lies with my iRule. Any suggestions on how to go about solving this issue? A better way to do the https redirect for the iframe content or a way of logging these events so I can perhaps notice a pattern in what kind of files are causing the issue or a way to redirect file uploads so they will work.
15 Replies
Sort By
- Hey Willy,
- Can you take an HTTPWatch or some similar capture so we can visualize what is going on? There's a few different possibilities.
- Just to make it easy to spot the error. The result column = 501 in the third section of the badupload screen capture is where to error message appears.
- Hey Willy,
- I see some mention of this error in Tomcat's bugzilla (https://issues.apache.org/bugzilla/show_bug.cgi?id=46984), but they mention it was fixed in 5.5 upward. At any rate, I'd open a support case on this - it'll go beyond just HTTPwatch I fear. One note: can you successfully upload smaller files? I see the working version is smaller than the broken one.
- -Matt
This has been fixed in 5.5.x and will be included in 5.5.28 onwards. I am using version 5.5.29 Thank you all for so much help.
- I'd be interested to see why your POSTs are getting 302 responses almost immediately.
- Is the last header/response pair in the screen above when the response is 501?
- Okay I have a theory. Let me know if this is totally out of left field. When the stream was rewriting. It would rewrite files that had a URL in them matching http:// this would make the files have different file sizes in transit and would cause a file size check somewhere to fail.
- [quote=Willy]okay this fixed the problem. Can someone help to explain how?
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects