Hide parameters after starting a web app

Hi everyone…
I need to hide the parameters sent to call a WebApp after it is called.
For instance: I need to start a WebApp that it is hosted on IP and in the port 9000 and passing 2 parameters
So the link will be something like:
I need to send these two parameters but I dont want that they remain visible at the url textfield at the top of the web browser after the web app starts.
Is possible to hide them ?

If you POST rather than GET then your parameters will be hidden and not in the URL

GET puts parameters in the URL itself (and can be insecure for calling as the parameters will also go into log files, etc)

POST is the calling method used to send web form contents to a server. The form fields are sent along with the request but not in the URL

If you look up how to POST using CURL from the command line you’ll see how it’s done.

if you don’t like CURL and want to do it from a browser, create a simple HTML web page file that has a in it and tags and submit button. Open the file into a browser and you can load it from there.


You could load the url and when you find your parameters store them somewhere like a database, or cookie, or session. Then redirect to and use the values you store previously.

@Hal Gumbert,
Sorry for the delay in responding… Your trick works fine.

Below is a code anyone could use to hide parameters passed to a WebApp and show instead for example an UUID, after launching the webapp

Lets say that the WebApp needs 2 parameters
You will need 3 parameters in order Hal’s trick to work
The second and third parameters are the usefull ones for the WebApp, the ones you nedd to pass to the WebApp, and the first one is an auxiliar parameter.
So you could call the WebApp as follows:
In the Session Open Event you load parameters and validate them
The first validation is between the auxiliar parameter and a Cookie that will be unsuccesfull the first time
so in the example it proceeds to evaluate if Param2=1234 and Param3=abcd and lets say thata they are the right ones.
If that happened the WebApp will set a Cookie with an aleatory string… in my case I used a UUID type random string
Then the WebApp is the auto reloaded only passing the auxiliar parameter with the UUID random value
The Session Open Event is again excecuted because of the reloaded of the WebApp but noe with the auxiliar parameter only
and the validation will be this time between the UUID and the Cookie Value, beeing in this case successfull too
And at that time the WebApp finally starts with the original parameters unvisible and with an aleatory UUID as a parameter shown in the urltextfield of the browser

Code to be placed in the Session Open Event

If Self.URLParameterCount > 0 Then
Dim parameterName(3), value(3) As String
For i As Integer = 0 To Self.URLParameterCount-1
parameterName(i) = Self.URLParameterName(i)
value(i) = Self.URLParameter(parameterName(i))
if Value(0)=Session.Cookies.Value(“UUID”) then
msgbox “Here is the succesfull access hiding the initial parameters”
if Value(1)=“1234” And value(2)=“abcd” then
Session.Cookies.Set(“UUID”, GenerateUUID)
ShowURL(“” + Session.Cookies.Value(“UUID”))
end if
end If
end if