I am running into the same issue as described form the post: https://community.progress.com/community_groups/openedge_development/f/19/p/37128/115774
This was almost 2 years ago and in that thread it said there was a hotfix but I am currently running PASOE 12.1 and still getting this issue.
I have tried the same things as the prior post with a "302" and "302 Redirect" headers but still always get a 200 back.
Is this still a known issue and some sort of tech support ticket is required to get a hotfix to apply?
The referenced post menions PSC00357125 - which was released in 11.7.3 and 12.0 - see knowledgebase.progress.com/.../pasoe-compatibilityhandler-not-returning-correct-http-status-code
The referenced post menions PSC00357125 - which was released in 11.7.3 and 12.0 - see knowledgebase.progress.com/.../pasoe-compatibilityhandler-not-returning-correct-http-status-code
The following link was the answer: knowledgebase.progress.com/.../pasoe-compatibilityhandler-not-returning-correct-http-status-code
I've been very disappointed with PAS OE, trying to convert over our legacy webspeed programs has been a nightmare - it's like progress is going backwards with web technologies.
The workaround in the thread where I reported the issue still appears to work. We use code something like this in old WebSpeed logic to handle the redirects:
// If PASOE Agent, generate new style header IF multi-session-agent() THEN output-http-header("","HTTP/1.1 302 Redirect"). ELSE output-http-header("Status","301" + " Redirect"). output-http-header ("URI",p-loc). output-http-header("","").
We are no longer using old WebSpeed. There were a number of things we had to tweak to get our old WebSpeed programs running under PASOE, but they do work.
Happy New Year!