Forum Discussion
Jason_Keating
Mar 31, 2010Altostratus
Yeah, I'd say that WLS is throwing that 500, in your response the " " gives it away.
The F5 is not generating the error, simply passing it back to you as it should.
Assuming you can point a browser or some other client at WLS (curl, netcat, telnet ...) and do not get this error when sending the request direct to WLS you should compare the request passed by your browser to WLS (when not using the LTM) to the request passed by the LTM to WLS (when using the LTM)
If you do get the error when GET'ing from WLS with no LTM - look to WLS.