This Q&A forum allows users to post and respond to "How Do I Do ....." questions. Please do not use to report (suspected) errors - you must use your regional help desk for this. The information contained in this forum has not been validated by LANSA and, as such, LANSA cannot guarantee the accuracy of the information.
We tried to do something similar without much success, simply could never get the server redirection working right.
Ended up with a client redirection solution which is not ideal as the URL changes, but it works for us.
Had some discussion regarding it here viewtopic.php?f=3&t=1193&p=2097. Brendan mentioned a way by modifying the httpd.conf of the web server.
Danny talked about one way of having an "friendly url" here viewtopic.php?f=4&t=47.
I don't know how / if VLF-ONE will have an impact on that technique.
Just thinking here, but you may be able to create a simple html page with an iframe in it that points to the VLF-ONE page .... ?
Before posting I read your "vanity URL" and related posts. Interesting stuff, but not exactly what I was looking for. Since the Apache manuals say it is possible, I imagine there is just some twist that IBM did (or didn't do) for the IBM i version.
These are the modifiers for rewrite rules on Apache on IBMi.
NC = not case sensitive
PT = pass thru
R = redirect
L = Last
N = Next
Instead of this...
RewriteRule ^/POSWeb$ /DCZPGMLIB/ITG/ABC_OEXEC.HTML?Lang=ENG&FrameworkID=ABC_SYSTEM&material=Y [L]
Do this
RewriteRule ^/POSWeb$ /DCZPGMLIB/ITG/ABC_OEXEC.HTML?Lang=ENG&FrameworkID=ABC_SYSTEM&material=Y [NC,PT,L]
I typically use not case sensitive (NC) because you really don't want that.
Last (L) is optional unless you want it to do no more rewrites. If the rules never overlap this is not typically a problem, but I left it in anyway for your example.
The important bit is the PT which doesn't redirect the browser to a new page, but instead does the redirect internally, and the user never sees it.
This makes it really hard to debug if something goes wrong. During development I will use the R so I can see what is going on, but then for QA and staging and finally production I will switch from redirect (R) to pass thru (PT).
I'm still learning all this HTTP Server magic - I'm trying to support both SSL and non-SSL versions in the same config. At the moment, I can't figure out how to conditionally switch the ports as needed. I'll research Alias tomorrow within the different VirtualHost containers in the configuration.