Search results

I've figured it out. Not sure if this is the correct method, but it worked. DEFINE VARIABLE oResHeader AS OpenEdge.Net.HTTP.HttpHeader NO-UNDO. oResHeader = NEW OpenEdge.Net.HTTP.HttpHeader("Location","OAuthFailure.html"). oResponse:StatusCode...

I've spent the last few hours trying to figure out how to do a simple URL redirect from the PASOE WebHandler. In the Classic WebSpeed I would do somthing like this: <SCRIPT LANGUAGE="SpeedScript"> PROCEDURE output-headers: OUTPUT-HTTP-HEADER("Status","302")...

I'm not saying this is the answer, but it might point you in the right direction. Place this code in the MAIN-BLOCK after the "RUN enable_UI.": Frame DEFAULT-FRAME:VIRTUAL-WIDTH-PIXELS = C-WIN:Width-pixels - System.Windows.Forms.SystemInformation:BorderSize:Width. Frame...

I've toyed around with the idea of having a real-time messaging in a GUI App using MQTT. But, I lost interest due to lack of business requirement and really wanted to use an opensource .NET assembly the that had done all the hard work for me But, unfortunately due to the lack of multi-threading...

My mistake... I was using the 11.7 code. The "WriteStartLine" override method worked! BTW.. I also try using HAR tracing and crashed when output the when connecting to a proxy server. Separate issue to this.

This is my code and I think I've followed your instructions, but unfortunately I getting this error (See Bellow). /*------------------------------------------------------------------------ File : DefaultRequestFilterOverride Purpose : Syntax : Description ...

11.7.20.0.2288 was the version that was working. It almost need to have an override option to not use absolute URI when connecting via a proxy Server.

This is very odd. I've gone through the different revisions of OpenEdge.Net.HTTP.Filter.Payload.DefaultRequestFilter on GitHub and you are correct. There has been no changes in the logic of when to output a absolute URI vs. a relative URI when connecting via a proxy server. So, I'm not sure...

Thanks Peter. Would you a agree that it is a change in behavior between 11.7 and 12.8 when a client connects via a proxy server.

I've found this. HTTP/1.1: Request And by my interpretation, It seems that OE 12.8 is working according the RFC. If you make a request via a proxy server the URI can be an absolute URI. Servers MUST accept the absolute URI form in requests, even though HTTP/1.1 clients will only generate them...

Thanks, I'm now eyeballs deep looking at GitHub Repos. I'm using the same TLS 1.2 and the same ciphers.

I have existing code that has been working as expected on OE11.7. The code makes a simple POST request via a proxy server. Since upgrading to 12.8 the POST request is different and responds with a 404 http error code. OE 11.7 via a proxy, returns HTTP 200 POST /gateway/oauth/token HTTP/1.1...

I'm not 100%, but try adding a client startup parameter -cpstream UTF-8 -cpinternal UTF-8.

Simplified the code sample. /* Include the necessary namespace for JsonArray */ USING Progress.Json.ObjectModel.*. DEFINE VARIABLE myParser AS ObjectModelParser NO-UNDO. DEFINE VARIABLE oJsonArray AS JsonArray NO-UNDO. DEFINE VARIABLE iArrayLength AS INTEGER NO-UNDO. DEFINE VARIABLE...

/* Include the necessary namespace for JsonArray */ USING Progress.Json.ObjectModel.*. DEFINE TEMP-TABLE ttFruit FIELD fruit AS CHARACTER . DEFINE VARIABLE cCharExtent AS character NO-UNDO extent 4 INITIAL ["Apple","Banana","Cherry","Date"]. DEFINE VARIABLE oJsonArray AS JsonArray...

Output the file in batch mode (or via an AppServer) and and have the following client start up parameters. -noutf8warning -cpstream UTF-8 -cpinternal UTF-8

Are the put-shared-value & get-shared-value procedure located in a persistent procedure? I believe that I can re-produce the issue that you are experiencing. I think it's how you are persistently storing the last known widget handle in the super procedure that is causing you the issue. I'm...

I've not tested it, but try this: ... RUN put-shared-value("CUR-STATUS-MSG-HANDLE", STRING(l-wh)). END. /* of "IF NOT VALID-HANDLE(l-wh)" */ ELSE ASSIGN l-wh:SCREEN-VALUE = p-text l-wh:FRAME = p-frame-wh // Reaffirm the frame attribute if it's changed or not...

run cmd in administrator mode and user "netstat -ab" and see what ports are open.

Thinking outside the box. Does the PBX system that you have a HTTP callback/webhook option? If so, you can then use it in combination of PASOE. I've a had a quick look a the TAPI documentation and its a midfield of information. The only issue you might face is a continuing blocking process...