Proxy request to "real" webservice

[Roy de Kleijn]

Hello,

I see the following error occurring in my application:

Caused by: org.apache.cxf.transport.http.HTTPException: HTTP response '403: Forbidden' when communicating with http://localhost:9991/path


My configuration is as follows:

{
  "priority": 3,
  "request": {
    "method": "POST",
    "urlPattern": "/path"
  },
  "response": {
    "headers": {
      "Connection": "Keep-Alive",
      "Content-Type": "text/xml;charset=UTF-8",
      "Keep-Alive": "timeout=10, max=100",
      "Server": "Apache-Coyote/1.1"
    },
    "proxyBaseUrl": "https://realService.com"
  }
}

I see this in the console output from wiremock:

After request is coming in:
2015-08-28 09:44:49.593 Proxying: POST https://realService.com/path


What did I do wrong? how can we debug this?


Thanks,
Roy

[Tom Akehurst]

Can you post the request you're making to WireMock?

I suspect it's the service you're proxying to that's returning the 403. I can't think of any circumstance in which WireMock would do that unless you explicitly configure a stub that way.

[Roy de Kleijn]

The "real" service is responding without using wiremock. (with the same request)

Do we have to set additional headers? like referer?


Below is the request. It's confidential information, so I can't share the exact content.

POST /path HTTP/1.1
Content-Type: text/xml; charset=UTF-8
Accept: */*
SOAPAction: "urn:confidentialAction"
User-Agent: Apache CXF 2.4.8-patch-01
Cache-Control: no-cache
Pragma: no-cache
Host: localhost:9991
Connection: keep-alive
Content-Length: 1173

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><confidential body></soap:Body></soap:Envelope>
2015-08-28 21:47:01.836 Proxying: POST https://realService.com/path

[Tom Akehurst]

Without knowing more about the target system, it's hard to say.

One thing I'd suggest doing is getting logging configured and turning org.apache.http.* up to DEBUG so that you get all the HTTP traffic from WireMock's proxy logged out.

[Roy de Kleijn]

Will try that, but which file do I have to add to the class path?

[Roy de Kleijn]

One more thing: this is about forward proxying HTTPS requests..

[Tom Akehurst]

You can't forward proxy HTTPS, at all. Some proxies will let you work around that by turning into a TCP proxy via the CONNECT method, but that would be no use to WireMock as it needs to see the (unencrypted) contents of the request to be able to do anything useful.