Recent content by peterjudge

Your scrollbar is coming from the WITH phrase on the FORM statement. If you reduce it to something that fits into the window you will not see the scrollbar. You can also use the STATUS statement to write helpful texts.

If you don't want to lose any characters, then encoding is the way to go. Percent (URL) encoding doesn't handle the higher ranges of the codepoints. If you don't care about losing characters, you can walk through the strings character-by-character and ignore those that don't fit into 1251 (or...

There are the HTTP client classes available in 11.7. These have URL encoding available , via the OpenEdge.Net.URI class. You'll need to make sure that $dlc/gui|src|tty/netlib/OpenEdge.Net.pl is in PROPATH. There is also a OpenEdge.Core.Util.UTF8Encoder class which will encode UTF-8. By default...

You should add a WHERE clause, similar to the below. DEFINE VARIABLE dStartDate AS DATE NO-UNDO. DEFINE VARIABLE dEndDate AS DATE NO-UNDO. dStartDate = 3/1/2025. dEndDate = 4/1/2025. FOR EACH _aud-audit-data NO-LOCK WHERE _aud-audit-data._audit-date-time >= dStartDate AND...

The value in the runtimeconfig file must match a .NET version that's installed. If you specify 6 when only 8 is installed, bad things happen.

Was going to ask if that existed. The server connect method usually gets these things before the client socket for some reason, so knowing that it's in the HTTP client typically means it's the in the other clients. YMMV, ceteris paribus, etc

Can a moderator move this thread into the appropriate forum? I feel like we're beyond Chit Chat ...

You can take a look at Progress Documentation for some examples. Your description is a little confusing: you mention GUI clients and a web application. What are the client types involved here? GUI? Web? Both? (there's no wrong answer here but it does influence the PASOE and load balancer...

<putting my Tom hat on> Surely anti-malware on Windows would be removing the OS?

You don't mention the OE version, but the from 12.5 onwards, the ABL HTTP tracing feature I linked to can do all of this for you. You'd have to write a class to write the (JSON) trace data to a DB, but all the other bits are part of the OE product.

Sorry, I thought you'd assigned the writer to a variable ... define variable oWriter as OpenEdge.Net.HTTP.Filter.Payload.MessageWriter no-undo. oWriter = objMessageWriterBuilder:Writer. oWriter:Open(). oWriter:Write(RequestObj:Entity). oWriter:Close().

The bit you're missing is doing the writing of the Entity (payload) to the ByteBucket. Passing the message to the Build() method is effectively only doing the set up for the kind of writer to use for that message (ie is it JSON or XML or something else). objMessageWriterBuilder:Open(). /*...

If you're on 12.5+, take a look at Progress Documentation . Alternatively you can do what you're doing and also convert the body to bytes using the BodyWriterBuilder which will give you a bytebucket instance that you can dump to disk.

As @jdpjamesp says, more info would be useful. The first place I'd look is at what caused the STOP condition in the agent.