[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Requestbuilder post returns statuscode 404 OE 11.7

  • Thread starter Thread starter Peter Judge
  • Start date Start date
Status
Not open for further replies.
P

Peter Judge

Guest
You can save yourself some code and create the URI like below oURI = new URI( 'https' , 'bl2p.notify.windows.com' ). oURI:AddQuery( "token" , 'AwYAAAD57FoHGPLsV4Z3UbF%2BHOUcwUsVYFJ%2Bhli2hLE5NLyL2AnJD50x9eitoUyYaMLasiPCvJyKY1cmFvSi0E%2BxFrQSPCmDEDL0019wmJSU9aKSKjR2f6MAlNlzd8t4iutjnjM%3D' ). In 11.7.3 there’s also a new Parse() method that takes a second parameter to indicate whether to URL-decode the incoming string (which happens by default). It’s this URL-Decoding on Parse() that causes the token value to get messed up. Just call oURI = OpenEdge.Net.URI:Parse(cchannel, no ). Method headers FYI. /** Parses a string containing a URI and creates a URI object from it @param character a string URI (eg Application Development and Deployment Technologies - Progress) @return URI A URI representation of the string. */ method static public URI Parse( input pcURI as character ): return URI:Parse(pcURI, true ). end method . /** Parses a string containing a URI and creates a URI object from it @param character a string URI (eg Application Development and Deployment Technologies - Progress) @param logical TRUE if the incoming strings should be URL-decoded @return URI A URI representation of the string. */ method static public URI Parse( input pcURI as character , input pDecode as logical ):

Continue reading...
 
Status
Not open for further replies.
Back
Top