由于这是一个多部分请求，并且您正在上传“文件”部分，因此您需要使用
request.getPart("userfile1");
对于您的请求中不属于“文件”类型的元素，例如 input type="text"，您可以通过 request.getParameter 访问这些属性。
请注意，Jetty 8.0.1 已经很老了，最新的 Jetty 版本（在撰写本文时为 8.1.12）包含一些重要的多部分处理错误修复。
如果您升级 Jetty 版本，您可能必须显式启用 Multipart 处理，因为 Jetty 更严格地执行 Servlet 3.0 规范 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=395000)，如果您正在使用 servlet，请使用 @MultipartConfig 注释。
对于处理程序，您必须在调用 getPart(s) 之前手动将 Request.__MULTIPART_CONFIG_ELEMENT 作为属性添加到您的请求中
if (request.getContentType() != null && request.getContentType().startsWith("multipart/form-data")) {
baseRequest.setAttribute(Request.__MULTIPART_CONFIG_ELEMENT, MULTI_PART_CONFIG);
}
这将允许您解析多部分请求，但是如果您以这种方式注入配置，则不会清除创建的临时多部分文件。对于 servlet，它由附加到请求的 ServletRequestListener 处理（请参阅 org.eclipse.jetty.server.Request#MultiPartCleanerListener）。
所以，我们要做的是在处理程序链的早期有一个 HandlerWrapper，如果需要，它会添加多部分配置，并确保在请求完成后清理多部分文件。示例：
import java.io.IOException;
import javax.servlet.MultipartConfigElement;
import javax.servlet.ServletException;
import javax.servlet.ServletRequest;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import org.eclipse.jetty.http.HttpMethod;
import org.eclipse.jetty.server.Request;
import org.eclipse.jetty.server.handler.HandlerWrapper;
import org.eclipse.jetty.util.MultiException;
import org.eclipse.jetty.util.MultiPartInputStreamParser;
/**
* Handler that adds the multipart config to the request that passes through if
* it is a multipart request.
*
* <p>
* Jetty will only clean up the temp files generated by
* {@link MultiPartInputStreamParser} in a servlet event callback when the
* request is about to die but won't invoke it for a non-servlet (webapp)
* handled request.
*
* <p>
* MultipartConfigInjectionHandler ensures that the parts are deleted after the
* {@link #handle(String, Request, HttpServletRequest, HttpServletResponse)}
* method is called.
*
* <p>
* Ensure that no other handlers sit above this handler which may wish to do
* something with the multipart parts, as the saved parts will be deleted on the return
* from
* {@link #handle(String, Request, HttpServletRequest, HttpServletResponse)}.
*/
public class MultipartConfigInjectionHandler extends HandlerWrapper {
public static final String MULTIPART_FORMDATA_TYPE = "multipart/form-data";
private static final MultipartConfigElement MULTI_PART_CONFIG = new MultipartConfigElement(
System.getProperty("java.io.tmpdir"));
public static boolean isMultipartRequest(ServletRequest request) {
return request.getContentType() != null
&& request.getContentType().startsWith(MULTIPART_FORMDATA_TYPE);
}
/**
* If you want to have multipart support in your handler, call this method each time
* your doHandle method is called (prior to calling getParameter).
*
* Servlet 3.0 include support for Multipart data with its
* {@link HttpServletRequest#getPart(String)} & {@link HttpServletRequest#getParts()}
* methods, but the spec says that before you can use getPart, you must have specified a
* {@link MultipartConfigElement} for the Servlet.
*
* <p>
* This is normally done through the use of the MultipartConfig annotation of the
* servlet in question, however these annotations will not work when specified on
* Handlers.
*
* <p>
* The workaround for enabling Multipart support in handlers is to define the
* MultipartConfig attribute for the request which in turn will be read out in the
* getPart method.
*
* @see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=395000#c0">Jetty Bug
* tracker - Jetty annotation scanning problem (servlet workaround) </a>
* @see <a href="http://dev.eclipse.org/mhonarc/lists/jetty-users/msg03294.html">Jetty
* users mailing list post.</a>
*/
public static void enableMultipartSupport(HttpServletRequest request) {
request.setAttribute(Request.__MULTIPART_CONFIG_ELEMENT, MULTI_PART_CONFIG);
}
@Override
public void handle(String target, Request baseRequest, HttpServletRequest request,
HttpServletResponse response) throws IOException, ServletException {
boolean multipartRequest = HttpMethod.POST.is(request.getMethod())
&& isMultipartRequest(request);
if (multipartRequest) {
enableMultipartSupport(request);
}
try {
super.handle(target, baseRequest, request, response);
} finally {
if (multipartRequest) {
MultiPartInputStreamParser multipartInputStream = (MultiPartInputStreamParser) request
.getAttribute(Request.__MULTIPART_INPUT_STREAM);
if (multipartInputStream != null) {
try {
// a multipart request to a servlet will have the parts cleaned up correctly, but
// the repeated call to deleteParts() here will safely do nothing.
multipartInputStream.deleteParts();
} catch (MultiException e) {
// LOG.error("Error while deleting multipart request parts", e);
}
}
}
}
}
}
这可以像这样使用：
MultipartConfigInjectionHandler multipartConfigInjectionHandler =
new MultipartConfigInjectionHandler();
HandlerCollection collection = new HandlerCollection();
collection.addHandler(new SomeHandler());
collection.addHandler(new SomeOtherHandler());
multipartConfigInjectionHandler.setHandler(collection);
server.setHandler(multipartConfigInjectionHandler);