Skip to main content

Have basic HTTP methods PUT / POST / DELETE any meaning for Uniface ?

Author: gianni.sandigliano@unifacesolutions.com (gianni)

I'm trying to understand if other basic HTTP methods PUT / POST / DELETE / TRACE / OPTIONS / etc have any meaning to Uniface WAS. As far as I've understood with current Uniface WebApplicationServer GET is the only method used...but I could be wrong! I did not find any references in current Uniface Library (9.6.X503) to the other methods. Working with others environment a Web Server can be activated with the other methods...something like: HttpWebRequest request = (HttpWebRequest)WebRequest.Create ("http://myserver/mypath/myservice/?id=101"); request.Method = "POST"; request.ContentType = "application/atom+xml"; Stream requestStream = myHttpWebRequest.GetRequestStream (); requestStream.Write(newPost, 0, newPost.Length); requestStream.Close(); HttpWebResponse response = (HttpWebResponse)request.GetResponse(); if (response.StatusCode != HttpStatusCode.Created) { // Error }

Could Uniface WAS recognize a POST request like this? What will be the context at application level?
 
Can someone clean up my sky from the clouds?
SmileSmileSmile
 
Thanks,
Gianni

Have basic HTTP methods PUT / POST / DELETE any meaning for Uniface ?

Author: gianni.sandigliano@unifacesolutions.com (gianni)

I'm trying to understand if other basic HTTP methods PUT / POST / DELETE / TRACE / OPTIONS / etc have any meaning to Uniface WAS. As far as I've understood with current Uniface WebApplicationServer GET is the only method used...but I could be wrong! I did not find any references in current Uniface Library (9.6.X503) to the other methods. Working with others environment a Web Server can be activated with the other methods...something like: HttpWebRequest request = (HttpWebRequest)WebRequest.Create ("http://myserver/mypath/myservice/?id=101"); request.Method = "POST"; request.ContentType = "application/atom+xml"; Stream requestStream = myHttpWebRequest.GetRequestStream (); requestStream.Write(newPost, 0, newPost.Length); requestStream.Close(); HttpWebResponse response = (HttpWebResponse)request.GetResponse(); if (response.StatusCode != HttpStatusCode.Created) { // Error }

Could Uniface WAS recognize a POST request like this? What will be the context at application level?
 
Can someone clean up my sky from the clouds?
SmileSmileSmile
 
Thanks,
Gianni

Hi Gianni When you start an USP and ask for $webinfo("WEBSERVERCONTEXT") You'll get something like COMP=your_usp;SESSION=session_id;SERVERVARIABLES=... SERVER_NAME=your_server;SERVER_PORT=443;SERVER_PROTOCOL=HTTP/1.1;...REQUEST_METHOD=POST... If you write an empty USP (cleaning GetState and SetState) and with this in the Execute trigger: putmess $webinfo("WEBSERVERCONTEXT") $webinfo("OUTPUT") = "Wellcome to Chimichanga website!" Then you can experiment from SOAPui to call this "USP" using different methods.   Hope this helps


Author: luis.vila (luis.vila@uniface.es)

Have basic HTTP methods PUT / POST / DELETE any meaning for Uniface ?

Author: gianni.sandigliano@unifacesolutions.com (gianni)

I'm trying to understand if other basic HTTP methods PUT / POST / DELETE / TRACE / OPTIONS / etc have any meaning to Uniface WAS. As far as I've understood with current Uniface WebApplicationServer GET is the only method used...but I could be wrong! I did not find any references in current Uniface Library (9.6.X503) to the other methods. Working with others environment a Web Server can be activated with the other methods...something like: HttpWebRequest request = (HttpWebRequest)WebRequest.Create ("http://myserver/mypath/myservice/?id=101"); request.Method = "POST"; request.ContentType = "application/atom+xml"; Stream requestStream = myHttpWebRequest.GetRequestStream (); requestStream.Write(newPost, 0, newPost.Length); requestStream.Close(); HttpWebResponse response = (HttpWebResponse)request.GetResponse(); if (response.StatusCode != HttpStatusCode.Created) { // Error }

Could Uniface WAS recognize a POST request like this? What will be the context at application level?
 
Can someone clean up my sky from the clouds?
SmileSmileSmile
 
Thanks,
Gianni

Tnks Luis! I was exactly looking for that...and SoapUI either... Chimichanga cheers... Gianni


Author: gianni (gianni.sandigliano@unifacesolutions.com)

Have basic HTTP methods PUT / POST / DELETE any meaning for Uniface ?

Author: gianni.sandigliano@unifacesolutions.com (gianni)

I'm trying to understand if other basic HTTP methods PUT / POST / DELETE / TRACE / OPTIONS / etc have any meaning to Uniface WAS. As far as I've understood with current Uniface WebApplicationServer GET is the only method used...but I could be wrong! I did not find any references in current Uniface Library (9.6.X503) to the other methods. Working with others environment a Web Server can be activated with the other methods...something like: HttpWebRequest request = (HttpWebRequest)WebRequest.Create ("http://myserver/mypath/myservice/?id=101"); request.Method = "POST"; request.ContentType = "application/atom+xml"; Stream requestStream = myHttpWebRequest.GetRequestStream (); requestStream.Write(newPost, 0, newPost.Length); requestStream.Close(); HttpWebResponse response = (HttpWebResponse)request.GetResponse(); if (response.StatusCode != HttpStatusCode.Created) { // Error }

Could Uniface WAS recognize a POST request like this? What will be the context at application level?
 
Can someone clean up my sky from the clouds?
SmileSmileSmile
 
Thanks,
Gianni

Hi Gianni, We make exclusive use of POST - because we don't want to show the parameters passed back to the server.... Of course the URL changes - but the $UUID's and params are not shown.


Author: Knut (knut.dybendahl@gmail.com)
Terms & ConditionsAccessibility statement