My company has an on-line workflow system that relies on ASP technology and PDF
technology.
At one point in the on-line workflow, the user is required to click a submit
button on a PDF form; the button does a standard HTTP submit to our server. The
server then generates an ASP page that is supposed to be displayed in the
user's browser.
This works fine for all of our users except one. (Well actually, we did have
another problem with it -- see my post on 2/23/2005 - "URL changes when submit
button is clicked" -- but we solved that problem by putting absolute URLs
instead of relative URLs into the ASP page that is displayed for the user after
the user clicks the submit button.) As for the one user that is having a
problem now -- what is happening with that user is this:
after he clicks the submit button, the HTML code resulting from the
interpretation of the ASP page does not display in his browser window unless he
clicks the browser's refresh button.
Our server is running IIS 5.0.
I have done a careful analysis of the relevant entries in the IIS log file on
our server. At this point in the workflow process, I see a log-file entry that
contains information something like this:
sc-status: 200
sc-bytes: 9726
cs-bytes: 611
time-taken: 201
All of this looks perfectly normal to me. Does anybody have any idea why this
particular user has to click his "Refresh" button to see the Web page that he
is supposed to see after clicking the submit button on the PDF form?
This particular user is running Windows XP Version 2002 SP1/IE Version
6.0.2800.1106.XP SP2 030422-1633.
- Cynthia Leslie
[Non-text portions of this message have been removed]
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/AspClassicAnyQuestionIsOk/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
