Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
CGI links broken in preview
System
iwserver: 5.5.2 Build 20638 Interwoven 20030604 on W2K.
I am previewing a templated page that contains links passing URL parameters to CGI scripts in the same workarea. When I view source of the page the links looks right, and if I paste those links into the same browser they work. But when I click on the link in the previewed content something apparently inserts garbage into the file name. For instance if my previewed content contains a link such as:
/cgi-bin/test/script.pl?p1=whatever&p2=whatever
when I click on this link it takes me to:
/cgi-bin/test/zz_tst_jwest_0_script.pl?p1=whatever&p2=whatever
where jwest is my username. IIS then apparently tries to execute this script and I get an error message that it does not exist.
If I generate the page the links work, it's only preview that has this bug.
There are no proxy rules here.
What is causing this? Is there any way to turn off the translation of my file names?
Apparently every link in previewed content gets translated into this zz_ rubish, then something on the back end removes it and this works for things other than Perl scripts. If Interwoven could provide an explanation...
Also, if I use href=javascript:window.location = whatever there is no problem, but that's pretty lame too.
Find more posts tagged with
Comments
Johnny
I've been caught with this problem before.
It's the way the proxy handles rewrites for previewing multiple ostreams (whether you have them or not)
basically in preview all urls are first rewritten to some zz_tst preview pattern first and usually if they fail it attempts to retrieve the original name.
There are some circumstances where the second step isnt processed. In my experience it did have to do with proxy pre connect maps catching the first pass.
IWOV did eventually acknowledge the problem after going through some tests with them.
Im not sure if they have addressed that problem as I was told i would be informed if it was. I dont think they gave it much priority as we came up with a workaround in our regexes.
Are you certain there are
no rules at all
for this in the proxy?...
Would be very strange other wise.
I added this to our regex lines to work around the issue
(zz_tst_[^_]+_[^_]+_)?
John Cuiuli
Migrateduser
> Are you certain there are no rules at all for this in the proxy?...
Only these two which don't seem to be related.
[iwproxy_fullproxy_redirect]
_regex=^http=
http://localhost/
[iwproxy_remap]
global_default_map=/
> I added this to our regex lines to work around the issue
Can you give an example?
Seems like something Interwoven should document, fix and/or provide some alternatives.
Thanks,
-John
Johnny
Is that you dancing around in sheeps clothing??...
_regex=^/iw-mount/[^/]+/main/([^/]+/)*([^/]+)/WORKAREA/([^/]+)/.*appl/(zz_tst_[^_]+_[^_]+_)?(.*)$=
http://localhost:7001/$2_$3_appl/$5
seems like whatever the url is
it will try and pre pend the zz_tst stuff before the filename so you need to make sure your regex will work in your circumstances.
The above example requires urls to be /appl/something_no_more_slashes
John Cuiuli
Migrateduser
> Is that you dancing around in sheeps clothing??..
I got bored of my imageless profiles. Still waiting for my wife to come up with new images.
Since this is only a problem for my files under /cgi-bin I will try to regex for that.
But of course I've already developed the workaround (javascript window.location thingy).
Thanks,
-John
Johnny
i would try running the proxy in debug mode to see how it determines its redirect.
Im not sure but it might be related to your redirect entry.
iwproxy -d -w some_other_port
will let you run a seperate proxy instance in debug mode
John Cuiuli
Migrateduser
Also, we have to be careful not to rewrite the page url we are trying to preview but to rewrite only the links referenced from the prview page. I guess this may do the trick. I didn't test it though.
_regex=^(/iw-mount/[^/]+/main/.*/WORKAREA/[^/]+/.*/iw_preview/zz_tst_.*)$=$1
_regex=^(/iw-mount/[^/]+/main/.*/WORKAREA/[^/]+/.*)/zz_tst_[^_]+_[^_]+_)(.*)$=$1/$2