Proxy issues on solaris

I am changing my previous post from webdesk to proxy since it seems that webdesk relies on the proxy, so it seems prudent to get this working first.

Our teamsite instance is version 5.5.2 SP3 on solaris...

If you try to click on any file in teamsite which is not a DCR, the window which pops up shows a url like:

http://10.202.4.32/iw/webdesk/sce?vpath=/default/main/aac/WORKAREA/Content+Block/templatedata/Content+Block/N%5fplain/BESS%5fbranding%5farea%5fjz.html

If you leave this browser window alone it will sit and sit and sit and never load anything. But! If you hit stop, the URL immediately changes to:

http://10.202.4.32/iw-mount/default/main/aac/WORKAREA/Content%20Block/templatedata/Content%20Block/N_plain/BESS_branding_area_jz.html

If I click reload with this new URL it will sit and sit forever. If I change the URL to:

http://10.202.4.32:81/iw-mount/default/main/aac/WORKAREA/Content%20Block/templatedata/Content%20Block/N_plain/BESS_branding_area_jz.html

Then the file I am trying to view comes right up. The file in question is an HTML file. I can't figure out why teamsite it not appending the port 81 in the URL once it resolves out of SCE... Any ideas?

Here is the proxy section of our /etc/iw.cfg file:

[iwproxy]
customer_webserver_host=10.202.4.32
iwproxy_host=10.202.4.32
iwproxy_port=1080
customer_webserver_port=81

And then our /etc/apache/httpd.conf file port entry:

#
# Port: The port to which the standalone server listens. For
# ports < 1023, you will need httpd to be run as root initially.
#
Port 81

So teamsite knows to look at port 81, and apache is listening at port 81.

Find more posts tagged with

Comments

nipper

Do you have a line this this:

Alias /iw-mount/ /.iwmnt/

in your httpd.conf file ?

Andy

BENMAY

Running:

tail httpd.conf

results in:

# PerlHandler Apache: Smiley Frustrated

tatus
# order deny,allow
# deny from all
# allow from yourhost
#</Location>
#
#</IfModule>
#

Alias /iw-mount/ /.iwmnt/

BENMAY

Doing a little further digging, I found the following by tailing the /etc/apache/logs/access_log file:

Here is the entry for the HTML file when I simply click the file from teamsite and the window pops up:

10.202.4.32 - - [24/Jun/2003:14:17:25 -0400] "GET /iw-mount/default/main/bom/WORKAREA/Search/templatedata/Search/SP_no_search_results/SP_no_search_results.jhtml HTTP/1.0" 200 8459
10.202.4.32 - - [24/Jun/2003:14:17:25 -0400] "GET /iw-mount/default/main/bom/WORKAREA/Search/templatedata/Search/SP_no_search_results/SP_no_search_results.jhtml HTTP/1.0" 200 8459

versus when I manually add the port 81 to the URL myself and hit return in the same popup window:

65.204.109.254 - - [24/Jun/2003:14:19:33 -0400] "GET /iw-mount/default/main/bom/WORKAREA/Search/templatedata/Search/SP_no_search_results/SP_no_search_results.jhtml HTTP/1.1" 200 8459

Now 65.204.109.254 is my personal PC. It would seem that when I try to view the file via SCE, apache is seeing the request, as witnessed by the entries with 10.202.4.32 (which is our teamsite instance). It looks as tho teamsite is unable to send the file to the browser window once it has recieved it from the apache instance?

Migrateduser

Try running iwproxy in debug mode. Kill the iwproxy processes (note that if you
just kill the child one, the parent will restart it), then run
$iwhome/bin/iwproxy -d.

Hopefully iwproxy will be able to tell you some more information about what is
causing the hang.

BENMAY

Have a look at the attached file, which shows the /var/apache/log/access_log entries for the proxy file requests, as well as the iwproxy -d output from same. Other than the fact that it is requesting the page twice, I don't see anything which indicates problems. Proxy is obviously communicating with apache, and recieving the file. In fact, if I control-c out of the proxy while the browser is hanging it will all of the sudden display the page finally. Very odd...