Bug 39656

Summary:	SOAP Action not set when HeaderManager is specified
Product:	JMeter - Now in Github	Reporter:	Davanum Srinivas <dims>
Component:	HTTP	Assignee:	JMeter issues mailing list <issues>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	P2
Version:	Nightly (Please specify date)
Target Milestone:	---
Hardware:	Other
OS:	other
Attachments:	Patch to set the soap action if it is not specified in the header manager

Description Davanum Srinivas 2006-05-25 09:00:26 UTC

Hi,

Could you please consider this tiny enhancement to add SOAPAction explicitly if
the user does not specify one in the header manager?

thanks,
dims

Comment 1 Davanum Srinivas 2006-05-25 09:01:08 UTC

Created attachment 18350 [details]
Patch to set the soap action if it is not specified in the header manager

Comment 2 Sebb 2006-05-25 15:30:04 UTC

Seems like a good idea - I'll try to add it shortly.

Comment 3 peter lin 2006-05-25 15:35:47 UTC

It's probably ok to add it if the user doesn't specificy a SOAPAction. To the
best of my knowledge, only .NET uses SOAPAction. Sun's JWSDP, apache axis,
apache soap, weblogic ws, IBM ws and several C/C++ webservice toolkit all ignore
soapaction. 

peter

Comment 4 Davanum Srinivas 2006-05-25 16:29:42 UTC

Axis2 uses SOAPAction :)

Comment 5 peter lin 2006-05-25 16:31:44 UTC

I wasn't aware that Axis2 now uses SOAPAction. I assumed axis2 is the same as
axis 1.x 

thanks for the info.

peter

Comment 6 Sebb 2006-05-25 16:48:39 UTC

Just wondering whether the GUI should always override the Header Manager - 
might that not be more useful?

Comment 7 Sebb 2006-05-26 17:18:42 UTC

After discussion, decided to always use the value on the GUI, whether or not a 
Header Manager is present, as this is how other samplers work (config items 
are used as defaults).

Code has been updated in 2.1 branch.
Nighttly build 2-1.20060526 contains the update.

Comment 8 The ASF infrastructure team 2022-09-24 20:37:37 UTC

This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1729