nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

iwproxy_plugin_remap for SSI remapping

mick

hi

we're running TeamSite 5.0.2 on Solaris with Apache as the web server.

i'm trying to get the iwproxy_plugin_remap working to virtualise files containing SSI directives that are trying to include files that only exist in another branch -- but i'm not having any luck :-(

Our branch structure is something like:

main
  |
  |-- branch1
         |
         |-- sub-branch2
         |-- sub-branch3
         |-- sub-branch4
         |-- etc ...

and the files we want to include exist in branch1 and sub-branch2 but not in any other sub-branch.

i would like users in workareas under sub-branch2 to be able to preview and virtualise the included files from their own workareas but users in all the other sub-branches should see the includes from branch1 staging area.

i've put the following entries into iw.cfg:

[iwproxy_plugin_remap]
_regex=/iw-mount/default/main/branch1/sub-branch2/WORKAREA/([^/]+)/include/(.*)=/iw-mount/default/main/branch1/sub-branch2/WORKAREA/$1/include/$2
_regex=/iw-mount/default/main/branch1/[^/]+/WORKAREA/[^/]+/include/(.*)=/iw-mount/default/main/branch1/STAGING/include/$1

and reset/restarted everything, but SSI requests don't seem to be getting redirected.

SSI requests for files that exist in the same workarea have always worked (since TeamSite was first installed for us) but there has never been any iwproxy_plugin_remap section in iw.cfg until now.

please help

mick :-)

Find more posts tagged with

Comments

kailash1

Did you stop all and start web server and then start teamsite.

--Kailash

mick

OK, it turns out that we're using the standard apache mod_rewrite module (not either of the iw_ts_rewrite modules that are mentioned in the manual) so any config under the iwproxy_plugin_remap section of iw.cfg is completely ignored!

we weren't involved in the initial set up and configuration of our TS server and it gets very frustrating when base functionality has been configured in some custom way that doesn't get a mention in the doco that was supposed to cover all customisations for the initial set up. i know that a lot of customisation has to be applied for our specific situation, and i'm currently doing a lot of this, but some of the things i've come across seem to be basic functionality that should be configured in a standard way as part of the initial installation -- and weren't!

[gets off soapbox] sorry, where was i ... that's right ... struggling with mod_rewrite syntax!

has anybody got any experience with this?

i've attached our mod_rewrite.conf file as it is at present. can anyone help with making it do what i outlined in my original post (but still retain the current functionality for other existing branches)?

i've had a bit of a play with it but we don't have a dev server, and i managed to break all SSI requests at one stage, so had to give up testing :-(

mick :-)