NoblePursuits's blog

HTTP Request Header "Authorization"

I have a working web services client against a commercial concern's website, and have a problem with a recent security change. They used to use "SOAPEndpointUserid and SOAPEndpointPassword", and have changed to a new authorization token, using a new HTTP Request Header with the name "Authorization".

I'm not the most web services savvy developer, and I haven't been able to figure out the 4GL changes needed. I developed the app using the prowsdldoc tool's output, but the output doesn't seem to reference http headers.

Can anyone point me in the right direction on this?


Why Can't I Use a Bullet Character - CHR(149) - MESSAGE alert-boxes?

They don't show, even though I am using the standard character set, and this is a standard ASCII character.

MESSAGE "This is a bullet:" CHR(149) VIEW-AS ALERT-BOX.
... shows no bullet.


Can't get schtasks.exe to work in Windows 7

I have a functioning command in Windows XP to schedule a task to run every minute with the Windows scheduler. It looks like this:

ASSIGN l-cmd = 'schtasks /Create /SC minute /RU "" /TN "Capture AutoSync" /TR "\"C:\Auto.lnk"'.
OS-COMMAND NO-CONSOLE VALUE(l-cmd).

On Windows 7, I get "The task XML is missing a required element or attribute."

However, the MS example (from their website) shows the following example:

SCHTASKS /Create /S system /U user /P password /RU runasuser
/RP runaspassword
/SC HOURLY /TN rtest1 /TR notepad


OS-COMMAND Fails Due to Windows Command-Line Parsing

I know I have seen the solution for this before, but I'll be darned if I can find it...

Windows does some funky parsing of command line parameters, requiring embedded quotes, tildas, etc. to pass a parameter that has embedded quotes from OS-COMMAND. Hoping somebody has the key.

Example:

l-db = "C:\My Folder\My Subfolder\My.db".
l-cmd = "C:\PROGRESS\OpenEdge\bin\prostrct repair " + l-db.

OS-COMMAND VALUE(l-cmd).

I've also tried:

l-db = "C:~"\My Folder~"\~"My Subfolder~"\My.db".
l-cmd = "C:\PROGRESS\OpenEdge\bin\prostrct repair " + l-db.


Super Procedures as a Replacement for Global Vars

I know that this seems so simple, I am almost embarrassed to even post it. I know how to create super procedures, and run them persistently. Can someone give me an example of how to use the technique to replace the need for global shared variables? I know I am missing something here! Thanks.


Syndicate content