Search results

OE 11.7.20 Windows 64bit. I'm a little bit late to the party but I'm slowly dipping my toe in my migrating existing classic WebSpeed code over to PASOE. The issue I'm having is that output header setting the http status to 302 is not working as expected I have found the knowledge base article...

I'm reopening this thread, because I though I saw a presentation about new features of 12.8 that it can now create YAML files. Only issue is that I can't remember where I saw this presentation (either as powerpoint or youtube). Can anyone confirm that 12.8 now supports the creation of YAML...

Is the Azure firewall open for port 4001?

No, I have not seen this spring add-on. I would not know how to incorporate it in with open edge.

I'm scoping out the prospect of implementing WebAuth into PASOE web transport. I can't see any existing implementation of this in OpenEdge and it seem that the SPRING Tomcat security framework is not able to handle WebAuthn. So, I've started going down the road of trying to "Roll-your-own"...

Shame that there is not plans to fix it.

I'm not sure if anyone else is experiencing this but, I've notice the Help search in the Openedge Developer Studio is almost unusable in version 12.8. I would select a keyword in the editor and bring up the context menu and click "Help on keyword" and the help search never brings up anything...

I found a workaround. From the developer studio I had to perform a full export of the ABL Web Services and then manually import the new Web Handlers. I'm not sure why this can't be pushed from the developer studio. Is this a bug?

Context migrating to 11.7 OE 12.8 I'm developing a new project and I'm creating a new ABL Service with it's associated web handler. The problem I'm facing is the the ABL Service is not getting Published to my local PASOE instance from the Developer Studio. Developer Studio goes through the...

There is possiblitly 170141183460469273745278895279919563358.9442406122

I have a requirement to convert an IPv6 address into a number (128bit number). Because it's a 128bit number I will have to store it in the database as a character field. I found some javascript code which does what I need, but for something so simple I can't figure out what need to do to...

I've updated the code on GitHub. I've altered things a bit and made it into a ABLOO static class object. GitHub - Jimbobnz/ABL-RC4: ABL RC4 (RC4) cipher I've crossed check the output with other RC4 utilities and it encrypts/decrypts as expected.

Hi Liza. Just so that I understand you correctly, the code sort of works but not 100% of the time? Is the ABL code working with the previously generated encrypted content? Is the content that you are trying to encrypt (or decrypt) text based or binary? When I wrote the first revision of the...

I've tested it with a binary file (1.2MB) and to my surprise it did work. However, it was very, very slow and that just because the ABL language is just not optimal for bitwise operations. Recommendation is to use an alternative encryption method which is supported by OpenEdge. If you do need...

Re-wrote using memptrs rather than concatenating character string values. It seems to be working well with larger string values too. It might possibly work with binary files aswell, but I have not tested that. Link the ABL DOJO...

Some Improvement to the code. Still has a bug where the source string can't exceed 261 characters. Possibly someone cleverer than me can spot the bug. FUNCTION bitXOR RETURNS INTEGER (INPUT X AS INTEGER, INPUT Y AS INTEGER): DEFINE VARIABLE b1 AS INTEGER NO-UNDO. DEFINE VARIABLE b2...

I've just written the algorithm ABL and tested it in ABL DOJO. Use it at your own risk. I've done about 2 mins of testing in the ABL DOJO. I think it also breaks when the string exceeds 112/113 characters. Until today I've never head of RC4 or ARC4. Hopefully, you can fix it. I do have a...

Alternative using .NET within the ABL. System.Windows.Forms.Clipboard:SetText("FooBar").

I won't be deploying the source code. At the moment it's a bit of a mixed bag of 11.7.x to 12.x.x.

Is this good practice to us the PROVERSION statement in this manor?: ASSIGN /* Only enable TLS1.3 if the Progress version is 12.8 or greater*/ cSSLProtocols[1] = "TLSv1.2":U cSSLProtocols[2] = "TLSv1.3":U WHEN PROVERSION GE "12.8" chCiphers[1] =...