|
Home > Archive > IIS Server Security > November 2004 > IIS 5.0 not accepting multipart/form-data
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
IIS 5.0 not accepting multipart/form-data
|
|
| CrazzyWebMonkey 2004-10-26, 5:50 pm |
| I have 3 IIS server set up (Development, Test, and Production), and each of
them behave differently when submitting a multipart/form-data form.
The Development server (using http://localhost/) works just fine, the file
is uploaded, and the rest of the fields are set just fine.
The Test server (using internal IP address) will send all the normal fields
just fine, but does not upload the file. No error is generated for the
browser, and the logs show a successful transaction (http: 302)
The Production server (using public IP address that is routed through a
firewall) does not upload the file, and does not send the rest of the fields,
and the browser displays an error (which varies depending on the language
used). When looking the web-logs, there is no error, in fact it shows that
the everthing went fine (http: 302)
Is this behavior caused by an IIS setting (or lack of setting) or a Windows
setting? Where could I find these setting at?
--
CrazzyCodeMonkey
| |
| David Wang [Msft] 2004-10-28, 7:48 am |
| Are all the IIS servers the same version, same patches, etc?
I suggest using Network Monitor to see traffic between separate client and
server doing the submit. This will tell you whether the data is sent by the
browser or not, whether it is received/processed by the server or not, etc.
Also use the same client machine as well as submit the exact same file to
remove client-side variance.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"CrazzyWebMonkey" <CrazzyWebMonkey@discussions.microsoft.com> wrote in
message news:598E4428-594A-434C-BB27-864AB50C3BD5@microsoft.com...
I have 3 IIS server set up (Development, Test, and Production), and each of
them behave differently when submitting a multipart/form-data form.
The Development server (using http://localhost/) works just fine, the file
is uploaded, and the rest of the fields are set just fine.
The Test server (using internal IP address) will send all the normal fields
just fine, but does not upload the file. No error is generated for the
browser, and the logs show a successful transaction (http: 302)
The Production server (using public IP address that is routed through a
firewall) does not upload the file, and does not send the rest of the
fields,
and the browser displays an error (which varies depending on the language
used). When looking the web-logs, there is no error, in fact it shows that
the everthing went fine (http: 302)
Is this behavior caused by an IIS setting (or lack of setting) or a Windows
setting? Where could I find these setting at?
--
CrazzyCodeMonkey
| |
| CrazzyWebMonkey 2004-10-28, 5:51 pm |
| All the version of IIS are the same, all are fully patched, and all have the
most recent virus definitions loaded. The forms that reside on the three
different servers (which is the exact same code) are all submitted from the
same machine by the same browser.
The Dev server is actually my Dell workstation, running Win2k Pro (hence the
use of http://localhost)
The Test server is a Dell server running Win2k Server.
The Production server is a Dell server running Win2k Server.
The browser I am using is Explorer 6.0.2800.1106.
As for using Network Monitor, or some other packet sniffer, I honestly don't
know what to look for. Some advice on what to look for would be appreciated.
When the forms are submitted to the production server from outside the
firewall, the same errors are received. The other 2 servers are protected by
the firewall, and so can't test them from outsite the firewall.
CrazzyCodeMonkey
"David Wang [Msft]" wrote:
> Are all the IIS servers the same version, same patches, etc?
>
> I suggest using Network Monitor to see traffic between separate client and
> server doing the submit. This will tell you whether the data is sent by the
> browser or not, whether it is received/processed by the server or not, etc.
>
> Also use the same client machine as well as submit the exact same file to
> remove client-side variance.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
| |
| David Wang [Msft] 2004-10-28, 5:51 pm |
| Is URLScan running on all the machines? With the same configuration file?
Any other software differences?
How large are the forms data being submitted? kilobytes, megabytes,
gigabytes ?
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"CrazzyWebMonkey" <CrazzyWebMonkey@discussions.microsoft.com> wrote in
message news:76EB3352-37B8-4C79-85D0-018B6A9CC111@microsoft.com...
All the version of IIS are the same, all are fully patched, and all have the
most recent virus definitions loaded. The forms that reside on the three
different servers (which is the exact same code) are all submitted from the
same machine by the same browser.
The Dev server is actually my Dell workstation, running Win2k Pro (hence the
use of http://localhost)
The Test server is a Dell server running Win2k Server.
The Production server is a Dell server running Win2k Server.
The browser I am using is Explorer 6.0.2800.1106.
As for using Network Monitor, or some other packet sniffer, I honestly don't
know what to look for. Some advice on what to look for would be
appreciated.
When the forms are submitted to the production server from outside the
firewall, the same errors are received. The other 2 servers are protected
by
the firewall, and so can't test them from outsite the firewall.
CrazzyCodeMonkey
"David Wang [Msft]" wrote:
> Are all the IIS servers the same version, same patches, etc?
>
> I suggest using Network Monitor to see traffic between separate client and
> server doing the submit. This will tell you whether the data is sent by
the
> browser or not, whether it is received/processed by the server or not,
etc.
>
> Also use the same client machine as well as submit the exact same file to
> remove client-side variance.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
| |
| CrazzyWebMonkey 2004-11-05, 5:50 pm |
| I actually found the solution to the solution on a Macromedia board
Using AC-MetaDataEditTool, I found that the UploadReadAheadSize was set to
0. Useing the MetaDataEditTool, simply delete this variable
(LM/W3SVC/UploadReadAheadSize) and it works fine.
CrazzyWebMonkey
"David Wang [Msft]" wrote:
> Is URLScan running on all the machines? With the same configuration file?
> Any other software differences?
>
> How large are the forms data being submitted? kilobytes, megabytes,
> gigabytes ?
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "CrazzyWebMonkey" <CrazzyWebMonkey@discussions.microsoft.com> wrote in
> message news:76EB3352-37B8-4C79-85D0-018B6A9CC111@microsoft.com...
> All the version of IIS are the same, all are fully patched, and all have the
> most recent virus definitions loaded. The forms that reside on the three
> different servers (which is the exact same code) are all submitted from the
> same machine by the same browser.
>
> The Dev server is actually my Dell workstation, running Win2k Pro (hence the
> use of http://localhost)
> The Test server is a Dell server running Win2k Server.
> The Production server is a Dell server running Win2k Server.
>
> The browser I am using is Explorer 6.0.2800.1106.
>
> As for using Network Monitor, or some other packet sniffer, I honestly don't
> know what to look for. Some advice on what to look for would be
> appreciated.
>
> When the forms are submitted to the production server from outside the
> firewall, the same errors are received. The other 2 servers are protected
> by
> the firewall, and so can't test them from outsite the firewall.
>
> CrazzyCodeMonkey
>
> "David Wang [Msft]" wrote:
>
> the
> etc.
> rights.
>
>
>
| |
| David Wang [Msft] 2004-11-06, 2:46 am |
| Hmm, UploadReadAheadSize is set to 49152 by default on all IIS versions, so
you ran some setup on the server that changed it.
It also means that your POST acceptor likely has a bug. What happens when
you POST data length > UploadReadAheadSize ? Try setting it to 1K and
posting 2K of data. My hunch is that the POST acceptor won't read 2K of
data. If so, this is a just a bug with the POST acceptor.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"CrazzyWebMonkey" <CrazzyWebMonkey@discussions.microsoft.com> wrote in
message news:3AE5B050-ACC3-431F-8D74-85B6D9E92773@microsoft.com...
I actually found the solution to the solution on a Macromedia board
Using AC-MetaDataEditTool, I found that the UploadReadAheadSize was set to
0. Useing the MetaDataEditTool, simply delete this variable
(LM/W3SVC/UploadReadAheadSize) and it works fine.
CrazzyWebMonkey
"David Wang [Msft]" wrote:
> Is URLScan running on all the machines? With the same configuration file?
> Any other software differences?
>
> How large are the forms data being submitted? kilobytes, megabytes,
> gigabytes ?
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "CrazzyWebMonkey" <CrazzyWebMonkey@discussions.microsoft.com> wrote in
> message news:76EB3352-37B8-4C79-85D0-018B6A9CC111@microsoft.com...
> All the version of IIS are the same, all are fully patched, and all have
the
> most recent virus definitions loaded. The forms that reside on the three
> different servers (which is the exact same code) are all submitted from
the
> same machine by the same browser.
>
> The Dev server is actually my Dell workstation, running Win2k Pro (hence
the
> use of http://localhost)
> The Test server is a Dell server running Win2k Server.
> The Production server is a Dell server running Win2k Server.
>
> The browser I am using is Explorer 6.0.2800.1106.
>
> As for using Network Monitor, or some other packet sniffer, I honestly
don't
> know what to look for. Some advice on what to look for would be
> appreciated.
>
> When the forms are submitted to the production server from outside the
> firewall, the same errors are received. The other 2 servers are protected
> by
> the firewall, and so can't test them from outsite the firewall.
>
> CrazzyCodeMonkey
>
> "David Wang [Msft]" wrote:
>
and[vbcol=seagreen]
> the
> etc.
to[vbcol=seagreen]
> rights.
>
>
>
|
|
|
|
|