This message was deleted.

Could you please share your configuration and the request.

\n

always suggests encoding issues

Thanks Oleg four your quick reaction. I was looking very hard at the test code I wrote and I realized my mistake 🙂. Basically before calling the Rest client operation, I was trying to add a NULL HTTP header, which was causing Grizzly to return 404 with that message. No further assistance is required. Cheers!

Happy to help!