POST vs. GET Call Structure

[Former Member]

SRM Experts,

I'm upgrading from EBP2.0 to SRM6.0 but I'm having trouble with external catalogs that once worked with a GET method but issueing a POST in 6.0.

The URL strings in 6.0 are much longer than the 1024 limit of most browsers as such SRM changes the request from GET to POST. It is not very secure either as all info is passed in the querystring. Is there a way(on the vendor side) to switch/update a catalog to accept POST connections to it versus just GET connections?

Thanks

[Former Member · Accepted solution]

Hi,

To be frank, GET & POST perform the same functionality but POST has the advantage for multi-coded data. http://www.w3.org/2001/tag/doc/whenToUseGet.html

"It is not very secure either as all info is passed in the querystring." -> The service provide should opt for HTTPS, SSL to get the connection more secured.

Is there a way(on the vendor side) to switch/update a catalog to accept POST connections to it versus just GET connections? -> You must check with the external catalog service provider for this requirement as it is completly based on their application (say servlets etc).

Regards

Kathirvel

[jason_boggans]

Hi,

Please ensure you have read and understood the note 1003026 which defines that only METHOD POST should be used:

Catalog providers must ensure that they post to a specific target which

is defined by SRM. This can be verified in the "form tag" in the HTML

that is sent by the catalog:

<form action="<Hook URL sent by SRM>" target="_top" method="POST">

[Note 1003026|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1003026]

Regards,

Jason