No I didn't have to setup any proxy between my client (a java program) and the website.
----- Original Message ----- From: "Warwick Burrows" <[EMAIL PROTECTED]> To: "'Slide Users Mailing List'" <[EMAIL PROTECTED]> Sent: Thursday, June 17, 2004 3:09 PM Subject: RE: Helpful technique for debugging > > Did you need to configure a proxy between TCP viewer and the client as it is > suggested that you do for the HTTP protocol on the website? > > Thanks, > Warwick > > > ----------------------------------------------------------- > Warwick Burrows E2open > Senior Engineer 9600 Great Hills Trail, #325 > http://www.e2open.com Austin TX 78759 > ----------------------------------------------------------- > > > -----Original Message----- > From: kranga [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 17, 2004 1:50 PM > To: Slide Users Mailing List > Subject: Helpful technique for debugging > > > Thought I'd pass along this helpful tip to debug your slide programs... > > Use a TCP Viewer to view the exact message exchange between your client and > the server. Westbrooksoftware.com has a shareware program called "TCP > Viewer" that is very easy to run. Just set its remote port to your slide > install's port (8080 for example) and the local port to something else (e.g. > 8000). Then have all your slide clients connect to the local port. All the > HTTP message traffic is then viewable and you can use the webDAV rfc or any > other source to easily verify what is going on... > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
