B
Brian
I have a frontpage form created in 2002, running 2002
exensions. This form was created based on the same
template that all of my numerous other forms were based.
The form is simple, the action for the form is hardcoded
as confirm.asp. It works most of the time.
However, on a few rare (but not rare enough for me to
dismiss it), the form with a referenced confirm.asp
action decides to try and make its action out to be a
directory level above where it actually is. For example,
the form at
http://server.com/_clientname/global/default.htm when
submitted will display
http://server.com/_clientname/confirm.asp. Well, that's
not where confirm.asp is. Like I said, it works most of
the time, and with identical form data it can give varied
results.
I'm an asp programmer supporting my frontpage users on
this, and I manually redid the html form and the asp
page, and it still misbehaves. This leads me to beleive
that it's a server extensions thing. We're running 2000
and 2002 extensions somehow (which I didn't even think
was possible, but I can't seem to fix it) on IIS 5 on
windows 2000 boxes running SP 4.
Has anyone else seen anything like this?
exensions. This form was created based on the same
template that all of my numerous other forms were based.
The form is simple, the action for the form is hardcoded
as confirm.asp. It works most of the time.
However, on a few rare (but not rare enough for me to
dismiss it), the form with a referenced confirm.asp
action decides to try and make its action out to be a
directory level above where it actually is. For example,
the form at
http://server.com/_clientname/global/default.htm when
submitted will display
http://server.com/_clientname/confirm.asp. Well, that's
not where confirm.asp is. Like I said, it works most of
the time, and with identical form data it can give varied
results.
I'm an asp programmer supporting my frontpage users on
this, and I manually redid the html form and the asp
page, and it still misbehaves. This leads me to beleive
that it's a server extensions thing. We're running 2000
and 2002 extensions somehow (which I didn't even think
was possible, but I can't seem to fix it) on IIS 5 on
windows 2000 boxes running SP 4.
Has anyone else seen anything like this?