Search results

It looks like you are missing the "transport" part of the request URI. That will be something like /rest/ or /web/ .

That was one of the structural changes I mentioned ... in 12.5 (I think) the type went from ByteBucket to RawMessage to support HAR tracing. The principle's the same, just make sure you use the correct version. You may nee to typecheck before casting if you want to use this class in 11.7 and 12.8..

A way to provide an override is as follows: 1. Create a class that extendes OpenEdge.Net.HTTP.Filter.Payload.DefaultRequestFilter (inherits from). 2. Override the WriteStartLine method. Copy & paste the original method in, and remove the lines that check for the existence of a proxy. DO NOT CALL...

It almost looks like there _was_ a bug in the 11.7 code which did not write the correct POST line. But it's hard to tell without some more debugging (I know that's just a variation on 'it depends'). Which exact 11.7 are you seeing the "good" behaviour in?

I would not have expected a behaviour change in this regard. There are some internal changes to the data structures used (and obviously other changes for various things) but the code that writes the start line URL has not changed between 11.7 and 12.8 as far as I can tell. // In...

The CONNECT request is (only) sent when proxying over https, so you should be seeing it in your case. You are not going to see that request written into the request and response txt files (or rather, they will be overwritten), but if you set the LOG-MANAGER LOGGING-LEVEL to 5 then you will see...

The PDSOE versions will be the OpenEdge version. So for 12.8 you will have version 12.8. The Eclipse version is whatever it is. You will need to get the installer from Progress' ESD site .

This is because the static code is loaded once per session and you cannot unload or force a reload. When you are testing, I would strongly recommend that you use a separate session/shortcut. That way you know that you are working on the most recent code. If you follow @Osborne 's suggestion...

There is a setting in the project settings that relates to "Modules" that I think may impact this path. Make sure that the AppServer folder is selected.

The Procedure Editor will use whatever settings the session is using. So you could add a file using the command line (Progress Documentation)

Check syntax does a compile behind the scenes :)

Ah, ok. The code documentation procegrams will include INPUT/INPUT-OUTPUT/OUTPUT as well as the datatype of the parameters. This is not done by the code documentation tools. They will look at the comments on the procedure and generate the documentation based on that.

You can automate which programs call which programs using the COMPILE XREF functionality. The compile XREF can tell you who calls who, as well as the parameters. I'm not sure what you are looking for here. For this, as well as probably the example of calling, you are going to want to look at...

This often means that you don't have the root CA certificate. You can see what that is using your browser (usually via clicking on the lock next to the URL bar). In this case, it's Go Daddy Root Certificate Authority - G2 . You should download and install that in the certs dir.

It's a hallucination. You can use an openclient (java or .NET) to call ABL on an AppServer. You can call .NET classes from ABL clients (over the "bridge"). You can call java classes that are exposed via something like the IKVM in .NET. But you cannot call java classes directly in ABL. In 12.8...

If you have the developer tools license you have access to both Appbuilder and PDSOE (Progress Developer Studio for OpenEdge, fka OE Architect). I'd assume this is the "OE Studio" your partner is referring to. You should have access to it - it's been in the OE product for many releases/years...

IMO PDSOE is notoriously flaky when publishing stuff. Some people have the correctly-coloured thumb to be able to publish consistently; I don't. If you're adding a webhandler to an 11.7 PASOE instance, and have access to the server, I would just add the handler line to conf/openedge.properties...

In addition to what @Stefan says, you will also replace your wtbman call with tcman (or pasman).

The WSA has moved into PASOE in OE 12.0+ . The "Classic" AppServer was removed from OpenEdge in 12.0 and replaced by PASOE. PASOE is also a Tomcat server, and you can deploy SOAP services to it using the same artifacts as for the WSA.

Why? Are there any significant differences between the executables or environments? The OP's command line should use the -b switch, for sure.