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; } } }

TeamSite 6.7.2 SP2 Issue with remap when used with a cgi form submit

Deemer

Can anyone confirm if remaps works on form submission. We have a branch for managing forms, SecureForms/WORKAREA/docs/, which contains HTML forms (perl, cgi), which execute scripts in the cgi-bin sub-branch, SecureForms/cgi-bin/WORKAREA/formscgi/. Our HTML forms call the script, which all needs to write form data to an output CSV .txt file, and return a "thank you" HTML response page to the citizen. Both the text file and the 'thank you" response page files cannot be found once theform "submit" is executed. The HTML form can find the cgi-bin .pl file, however, it loses the ability to remap back to the SecureForms/WORKAREA/docs/ folders to server the response page and update the CSV .txt file. I have tried placing both the response HTML file and the .txt file under the formscgi workarea too and it can't be found anywhere within the branch.

Note the following changes made:

"1. Following changes made to /etc/iw.cfg to remap any request for scripts to formscgi workarea or staging:
[iwproxy_preconnect_remap]
_regex=(.*)/SecureForms/WORKAREA/(.*)/cgi-bin/(.*)=/iw-mount/default/main/SecureForms/cgi-bin/WORKAREA/formscgi/$3
_regex=(.*)/SecureForms/STAGING/cgi-bin/(.*)=/iw-mount/default/main/SecureForms/cgi-bin/STAGING/$2

The remapping only works for relative links on any file under SecureForms branch and will not remap absolute links from https://meteor.sannet.gov/ from any other branch.'

**This doesn't appear to be completely relative between the SecureForms and the SecureForms/cgi-bin files.

Can someone offer any insight to this issue?
Thank you!

Find more posts tagged with

Comments

nipper

Have you put iwproxy in debug mode to see what is happening ?

The other thing to consider is build a very small, simple CGI with corresponding HTML page. Something that will show the problem and others can test. Make it quite simple that can run on *any* system (i.e. don't just drop 500 lines of code dependent on 10 perl modules).

That will enable you to have support replicate it in case it truly is a bug.

Deemer

To the best of my knowledge, we are not running iw.cfg with debug.

I will look at the script I've been using, but while it does require perl, I don't believe it requires anything more than the standard library. Many of our scripts were writting years ago, and are quite basic.

I'll have to see what I can do to produce a simplified script if you think it's necessary.

thank you

nipper

OK, read the Admin manual about putting iwproxy into debug

What OS are you running ?

Basically you need to kill iwproxy (as admin or root) and then start it from a command line (with a lot of room to scroll or you can probably redirect the output to a file)

iwproxy -d

It will dump a lot of information when run, so do this on your dev server not prod, barring that, keep people off while you run your test.

Open your CGI and use the form, the proxy will output what URLs it gets and how it is processing them. From that information you can make some decisions about how the proxy statements should work.

HTH

Andy

Deemer

I will give that a try. Thahk you.

Deemer

We have run iwproxy in debug mode, but the output doesn't seem to be any more helpful that what I was able to determine in my testing paying attention to the URLs.

The script executes to a certain point, but when it comes to finding files in another area, it "gets lost".

It appears that we may need an additional regex to remap from the cgi-bin sub branch back to the main branch docs workarea. The question in doing that is how to keep the path references relative in the code aboiding the need to change them from testing in the workarea, staging and then for final production deployment.

Help!

test_modified_1.rptdesign

test_modified_1.pdf

nipper

Well you are not providing much information to be able debug anything.

Can you cut and paste the submit part of the proxy log ?

If the proxy won't help here, then I am afraid you will be required to hard code URLs. If server = "TS" URL =...., etc

test_modified_1_Jesse.pdf