Home/ Questions/Q 75759
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T20:33:59+00:00

Is it allowable to pass parameters to a web page through the URL (after

  • 0

Is it allowable to pass parameters to a web page through the URL (after the question mark) when using the POST method? I know that it works (most of the time, anyways) because my company’s webapp does it often, but I don’t know if it’s actually supported in the standard or if I can rely on this behavior. I’m considering implementing a SOAP request handler that uses a parameter after the question mark to indicate that it is a SOAP request and not a normal HTTP request. The reason for this that the webapp is an IIS extension, so everything is accessed via the same URL (ex: example.com/myisapi.dll?command), so to get the SOAP request to be processed, I need to specify that ‘command’ parameter. There would be one generic command for SOAP, not a specific command for each SOAP action — those would be specified in the SOAP request itself.

Basically, I’m trying to integrate the Apache Axis2/C library into my webapp by letting the webapp handle the HTTP request and then pass off the incoming SOAP XML to Axis2 for handling if it’s a SOAP request. Intuitively, I can’t see any reason why this wouldn’t work, since the URL you’re posting to is just an arbitrary URL, as far as all the various components are concerned… it’s the server that gives special meaning to the parts after the question mark.

Thanks for any help/insight you can provide.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Lets start with the simple stuff. HTTP GET request variables come from the URI. The URI is a requested resource, and so any webserver should (and apache does) have the entire URI stored in some variable available to the modules or appserver components running within the webserver.

    An http POST which is different from an http GET is a separate logical call to the webserver, but it still defines a URI that should process the post. A good webserver (apache being one) will again make the URI available to whatever module or appserver is running within it, then will additionally make available the variables which were sent in the POST headers.

    At the point where your application takes control from apache during a POST you should have access to both the GET and POST variables and be able to do whatever control logic you wish, including replying with a SOAP protocol instead of HTML.

    • 0