Soap Monitor

There is a known issue with configuring a standard SOAP monitor with a SOAPAction header value. See this post for details:

 

 

soap monitor failing

 

http://devcentral.f5.com/Default.aspx?tabid=53&forumid=32&tpage=1&view=topic&postid=29329

 

 

Aaron

Ahh Thanks Aaron, sorry to repost.. I didn't catch it in my search...

 

 

Anyways, any plans to fix other than upgrading to 10x?

 

 

No worries. I never got any detail on this CR. If you'd like to get more info and status on any potential fix in 9.x, you could open a case with F5 Support. I'd be interested in finding out why the bug exists. So if you do open a case, can you post back here with what you find out from F5?

 

 

Thanks,

 

Aaron

Sure thing.. I opened up a case and I'll let you know the results.

 

 

Thanks!

Support is correct here, if I recall. The RFC makes sense though: the SOAP-Action header is actually optional according to the RFC because you can't assume that SOAP will be using HTTP as a transport; it's supposed to be transport agnostic so you can't lock it into HTTP like that.

 

 

Now that being said, I'd really like to be able to set that header via a standard monitor setup. Most HTTP-transport SOAP implementations do in fact expect a soap action header, so this would be handy to have. The alternate is to use an external monitor and set this manually, which seems a little bit like a waste to me...

 

 

-Matt

If you can, post that CR number and I'll open a case as well and reference it. If anyone else out there finds this useful, please do the same and maybe we'll get this pushed into the product.

 

 

-Matt

642874

 

 

Thanks bud!