使用Jersey客户端的PATCH请求

我想执行我们的服务器支持的PATCH请求,以便使用Jersey客户端进行测试。 我的代码如下,但我得到com.sun.jersey.api.client.ClientHandlerException: java.net.ProtocolException: HTTP method PATCH doesn't support outputexception。 有人能让我知道下面的代码有什么问题吗?

 String complete_url = "http://localhost:8080/api/request"; String request = "[{\"op\":\"add\", \"path\":\"/name\", \"value\":\"Hello\"}]"; DefaultClientConfig config = new DefaultClientConfig(); config.getProperties().put(URLConnectionClientHandler.PROPERTY_HTTP_URL_CONNECTION_SET_METHOD_WORKAROUND, true); Client client = Client.create(config); WebResource resource = client.resource(complete_url); ClientResponse response = resource.header("Authorization", "Basic xyzabCDef") .type(new MediaType("application", "json-patch+json")) .method("PATCH", ClientResponse.class, request); 

这是完整的例外,

 com.sun.jersey.api.client.ClientHandlerException: java.net.ProtocolException: HTTP method PATCH doesn't support output at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:155) at com.sun.jersey.api.client.Client.handle(Client.java:652) at com.sun.jersey.api.client.WebResource.handle(WebResource.java:682) at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74) at com.sun.jersey.api.client.WebResource$Builder.method(WebResource.java:634) at com.acceptance.common.PatchTest.patch(PatchTest.java:42) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: java.net.ProtocolException: HTTP method PATCH doesn't support output at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1021) at com.sun.jersey.client.urlconnection.URLConnectionClientHandler$1$1.getOutputStream(URLConnectionClientHandler.java:238) at com.sun.jersey.api.client.CommittingOutputStream.commitStream(CommittingOutputStream.java:117) at com.sun.jersey.api.client.CommittingOutputStream.write(CommittingOutputStream.java:89) at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202) at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272) at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:276) at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:122) at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212) at java.io.BufferedWriter.flush(BufferedWriter.java:236) at com.sun.jersey.core.util.ReaderWriter.writeToAsString(ReaderWriter.java:191) at com.sun.jersey.core.provider.AbstractMessageReaderWriterProvider.writeToAsString(AbstractMessageReaderWriterProvider.java:128) at com.sun.jersey.core.impl.provider.entity.StringProvider.writeTo(StringProvider.java:88) at com.sun.jersey.core.impl.provider.entity.StringProvider.writeTo(StringProvider.java:58) at com.sun.jersey.api.client.RequestWriter.writeRequestEntity(RequestWriter.java:300) at com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:217) at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:153) 

这是当前JDK实现中的一个错误,已在JDK8实现中修复。有关详细信息, 请查看此链接https://bugs.openjdk.java.net/browse/JDK-7157360 。 有一种方法可以解决这个问题,但泽西团队决定不修复它https://github.com/eclipse-ee4j/jersey/issues/1639

我能想到的2种解决方案

  1. 使用支持HttpPatch方法的Apache Http Client
  2. 使用Jersey Client PostReplaceFilter,但必须修改Container代码,并在发出post请求时包含值为PATCH的X-HTTP-Method-Override标头。 请参阅http://zcox.wordpress.com/2009/06/17/override-the-http-request-method-in-jersey/ ]

仅供参考 – 如果有人在泽西岛2遇到此问题,请参阅:

https://jersey.github.io/apidocs/latest/jersey/org/glassfish/jersey/client/HttpUrlConnectorProvider.html

并使用SET_METHOD_WORKAROUND属性,如下所示:

  Client jerseyClient = ClientBuilder.newClient() .property(HttpUrlConnectorProvider.SET_METHOD_WORKAROUND, true) ... etc ... 

让我永远找到这个 – 我想我可以帮助缩短其他人的学习曲线。

如果你正在使用HttpsUrlConnection (注意‘s’ ) – 那么设置HttpUrlConnectorProvider.SET_METHOD_WORKAROUND将不起作用。 继续阅读详细的解决方案。

在我的例子中,设置HttpUrlConnectorProvider.SET_METHOD_WORKAROUND属性导致NoSuchFieldException因为我的HttpUrlConnection实例实际上是类型: sun.net.www.protocol.https.HttpsURLConnectionImpl并且它是super: javax.net.ssl.HttpsURLConnection (inheritance自HttpUrlConnection )。

所以当Jackson代码尝试从我的连接实例super( javax.net.ssl.HttpsURLConnection实例)获取方法字段时:

 /** * Workaround for a bug in {@code HttpURLConnection.setRequestMethod(String)} * The implementation of Sun/Oracle is throwing a {@code ProtocolException} * when the method is other than the HTTP/1.1 default methods. So to use {@code PROPFIND} * and others, we must apply this workaround. * * See issue http://java.net/jira/browse/JERSEY-639 */ private static void setRequestMethodViaJreBugWorkaround(final HttpURLConnection httpURLConnection, final String method) { try { httpURLConnection.setRequestMethod(method); // Check whether we are running on a buggy JRE } catch (final ProtocolException pe) { try { final Class httpURLConnectionClass = httpURLConnection.getClass(); AccessController.doPrivileged(new PrivilegedExceptionAction() { @Override public Object run() throws NoSuchFieldException, IllegalAccessException { final Field methodField = httpURLConnectionClass.getSuperclass().getDeclaredField("method"); methodField.setAccessible(true); methodField.set(httpURLConnection, method); return null; } }); } catch (final PrivilegedActionException e) { final Throwable cause = e.getCause(); if (cause instanceof RuntimeException) { throw (RuntimeException) cause; } else { throw new RuntimeException(cause); } } } } 

我们得到一个NoSuchFieldException指出名为method的字段不存在(因为getDeclaredFields()带来了所有字段,无论它们是否可访问,但只针对当前类,而不是当前类可能inheritance的任何基类)。

所以我查看了Java的HttpUrlConnection代码,发现允许的方法是由私有静态 String []指定的:

  /* Adding PATCH to the valid HTTP methods */ private static final String[] methods = { "GET", "POST", "HEAD", "OPTIONS", "PUT", "DELETE", "TRACE" }; 

解决方案是使用reflection更改此方法数组:

  try { Field methodsField = HttpURLConnection.class.getDeclaredField("methods"); methodsField.setAccessible(true); // get the methods field modifiers Field modifiersField = Field.class.getDeclaredField("modifiers"); // bypass the "private" modifier modifiersField.setAccessible(true); // remove the "final" modifier modifiersField.setInt(methodsField, methodsField.getModifiers() & ~Modifier.FINAL); /* valid HTTP methods */ String[] methods = { "GET", "POST", "HEAD", "OPTIONS", "PUT", "DELETE", "TRACE", "PATCH" }; // set the new methods - including patch methodsField.set(null, methods); } catch (SecurityException | IllegalArgumentException | IllegalAccessException | NoSuchFieldException e) { e.printStackTrace(); } 

由于methods字段是静态的,因此更改其值适用于扩展HttpUrlConnection任何具体实例,包括HttpsUrlConnection

旁注:我更喜欢Java将PATCH方法添加到JDK或从Jackson中执行字段查找整个层次结构的变通方法。

无论如何,我希望这个解决方案能为您节省一些时间。