Proxy regex help needed

I've got a requirement in Templating (TS6.5, Windows) to generate output containing proprietary tags. I'd like to be able to virtualize previews and generated output in TeamSite (instead of converting the tags to the desired format during a workflow).

All I've got to do is is strip out these tags like this:


  <image src="pt://image/images/something.gif">    ... should turn into:
  <image src="/images/something.gif">

Where the heck do I put a regex to do this? The iwproxy_preconnect_remap section does not seem to be the place. Plus, an admin advised me that the presence of the ":" char has "special" meaning in this context that prevents this regex from every being fired up (but he could not elaborate).

Thanks in advance for guidance.

Find more posts tagged with

Comments

nipper

First, what is a browser finding at pt://image/... ?

For absolute URLs (img = http://foo/image/imge.jpg) you use the browser's proxy to point it to the TS proxy and then use the TS proxy to do the remap.

It is discussed in the Admin manual.

That *should* work in your case as well

HTH

ANdy

LeggMan

First, what is a browser finding at pt://image/... ?

For absolute URLs (img = http://foo/image/imge.jpg) you use the browser's proxy to point it to the TS proxy and then use the TS proxy to do the remap.

It is discussed in the Admin manual.

That *should* work in your case as well

HTH

ANdy

The "pt://image" thing was represented to me as an automagical tag in the Aqualogic portal environment that's used to fetch images off a separate image server.

Off to RTFaM now...
Thanks

Adam Stoller

I've got a requirement in Templating (TS6.5, Windows) to generate output containing proprietary tags. I'd like to be able to virtualize previews and generated output in TeamSite (instead of converting the tags to the desired format during a workflow).

All I've got to do is is strip out these tags like this:
  <image src="pt://image/images/something.gif">    ... should turn into:
  <image src="/images/something.gif">
Where the heck do I put a regex to do this? The iwproxy_preconnect_remap section does not seem to be the place. Plus, an admin advised me that the presence of the ":" char has "special" meaning in this context that prevents this regex from every being fired up (but he could not elaborate).

Thanks in advance for guidance.

I'd suggest running iwproxy in debug mode first to see what it displays when processing the image request before you try making changes - then try making the changes and run it in debug mode again and see what it looks like.

The main question is whether iwproxy processes it as "pt://image/images/something.gif", "http://iw-mount/pt://image/images/something.gif", "http://iw-mount/default/main/branch/WORKAREA/waname/pt://image/images/something.gif" or something else. Once you know how iwproxy is seeing the URI, you can start to figure out ways to adjust it.

For instance - if iwproxy sees the last string shown above - a regex like the following might work:

_regex=^(.*)/pt://(.*)$=$1/$2

LeggMan

Thanks for suggesting an approach. This runs counter to the first suggestion in this thread involving use of the browser's proxy and will be easier to implement if someone who can run the proxy in debug mode (I can't do this even on Dev) can figure out the regex.

nipper

Thanks for suggesting an approach. This runs counter to the first suggestion in this thread involving use of the browser's proxy and will be easier to implement if someone who can run the proxy in debug mode (I can't do this even on Dev) can figure out the regex.

You *may* need to do both. If the pt:// goes directly to another process, then it will never get to the iwproxy remap.

That is how you do an absolute path (http::/blah/img/image.jpg). I do not know how the pt: will be processed by the browser.

LeggMan

Nothing else is hooked into TeamSite to react to "pt://images" embedded in the HTML of template previews or generated files so this should be managed within the proxy alone. Meanwhile, I wonder when docs and debugging facilities will improve so less voodoo is involved in getting things to work... 7.1?

Thanks

Adam Stoller

Thanks for suggesting an approach. This runs counter to the first suggestion in this thread involving use of the browser's proxy and will be easier to implement if someone who can run the proxy in debug mode (I can't do this even on Dev) can figure out the regex.

If you cannot run this due to permissions - then find out who can (on DEV) so that you can get what you need done.