As one can expect if a frontend has “/“ in a string path parameter, this should be encoded, otherwise the server will not recognise the request pattern.
The weird thing DWAN backend is that if I run it from net-beans on my tomcat localhost, it must be encoded 2 times before sending, and when it is run on lux16 or lux 17 it must be decoded 3 times. Otherwise you will have 400 Bad request respond. Tomcats on my localhost,lux16, lux17 are all the same: 6.0.
Our hypothesis is that on my localhost you need 2 encodings because Jersey decodes it once (breakpoint in debugging shows that indeed, the path parameter I have is 1 time decoded). On lux16 and lux17 Apache container needs extra encoding, may be because of the following know issue, opined by Olaf (see the first comment):
https://java.net/jira/browse/JERSEY-329
As one can expect if a frontend has “/“ in a string path parameter, this should be encoded, otherwise the server will not recognise the request pattern.
The weird thing DWAN backend is that if I run it from net-beans on my tomcat localhost, it must be encoded 2 times before sending, and when it is run on lux16 or lux 17 it must be decoded 3 times. Otherwise you will have 400 Bad request respond. Tomcats on my localhost,lux16, lux17 are all the same: 6.0.
Our hypothesis is that on my localhost you need 2 encodings because Jersey decodes it once (breakpoint in debugging shows that indeed, the path parameter I have is 1 time decoded). On lux16 and lux17 Apache container needs extra encoding, may be because of the following know issue, opined by Olaf (see the first comment):
https://java.net/jira/browse/JERSEY-329