Search results

That is indeed the right way to go. Is there a reason you chose not to use oResponse:SetHeader("location", "OAuthFailure.html" ). ? The SetHeader method does the whole building of the HttpHeader object under the covers for you. The other thing to make sure of is that the method returns 0.

Alas, it's not that simple. Unless you want to spend your time writing dynamic code to manipulate temp-tables - and, sure, we all have a somewhat masochistic streak, what with being ABL programmers :D - you will need a temp-table definition in more than one piece of source code. We can argue...

FWIW ALT-L also works in the Riverside VSCode extension. And it is *extremely* hard to avoid include files when you want to use a temp-table definition in more than one program. IMO the price you pay is significantly less than the inevitable errors introduced when you need to edit the TT...

I am not quite so opposed to preprocessors and includes as Julian is, but you should stay well away from using arguments for procedures. They mean that you cannot run on r-code, only source (and are the underlying reason why the data dictionary requires a development license). Please don't go...

I understand that the rcode for VAR is the same as for DEFINE VARIABLE. So you might be able to run rcode compiled in 12.5 or whenever with a 12.2 runtime. Would not recommend or ever suggest that in anything but a toy environment, but might be a fun exercise.

3 letters vs at least 7 (d-e-f-<space>-v-a-r)

If you look at the documentation page for the CREATE BROWSE statement, you'll see an example of a ROW-LEAVE trigger.

This might be related (in a broad sense) to Progress Documentation . At one point the ability to have a governor on the agent memory was discussed, but it is not in the product. I wonder whether this Swagger doc is simply inaccurate documentation.

How is the PASOE instance started? Under which user?

.war files are a whole other beast. And you don't need PDSOE for them either. It's almost only for producing PAAR files that you need PDSOE.

PASOE source code is just ABL source code. No need for anything special to compile it. What you DO need PDSOE for, is for creating certain kinds of service artifacts (eg REST API).

It's less "clever" and more "enjoys suffering" :D

You should be aware that 11.6 - and tomorrow, all 11.x releases - is retired. The example you have in the attached hello.p looks like Classic WebSpeed code. It will not work with restbroker (aka the Rest Adapter aka the REST transport in PASOE). A simple program to return data for the rest...

The doc at Progress Documentation is also very good - it describes various configuration properties including how they relate to each other (especially important w.r.t timeouts).

Is there a central repo for smtpmail? Or is it truly distributed source control :P

If you want to continue using the PUT statement and want the data quoted, look at the QUOTER function. For you old 'uns here, is there any other example you can think of of a language function being 'imported' from a C program that Progress ships?

The output that you are showing is for different tables I assume. Are you sure they use the same program to write the data to disk? The first example might be using a PUT or DISPLAY statement, and not the EXPORT statement.

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...