471,075 Members | 762 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,075 software developers and data experts.

HTTP/1.1 400 when GET request length is over 260 bytes

Hi!

I get HTTP/1.1 400 Bad Request when I try to access a aspx-page running on
server 2003 SP1 from internet explorer 6 running on the same machine.

Here is the URL I am using:

http://www.myserver.com/20th-Century-Design/1900-talsdesign/Interior-design/Mid-century-modern/midcentury/Mid-century-design/midcentury-modern/Modern-Design/Modernism/Vintage-design/Img/508_1_632651758409835000/Arm-chair-Barbera-d'Argento-Designed-by-Paolo-Pallucco-for-Pallucco-Italia.aspx

If I reduce the length of the URL below 260 bytes, then I get a page missing
error (which is good, since it indicates that it passes through whatever
check is preventing it from working)

I get the impression that the aspx-engine never kicks in and that the 400
response is generated from within IIS. As far as I know an URL should be
able to be over 2k bytes.
I know that the URLScan utility (which is not installed) has a limitation on
the URL on 260 bytes...

the URL has been URL-Encoded (Server.URLEncode) so no invalid characters
should be in the URL. (I get the same error if I remove the '-character)

/Håkan
Oct 17 '06 #1
6 3471
long url's usually have long arguments. you are probably hitting limits on
the max length of a directory name or filename (255).

-- bruce (sqlwork.com)

"Håkan" <no***@nowhere.comwrote in message
news:u7**************@TK2MSFTNGP04.phx.gbl...
Hi!

I get HTTP/1.1 400 Bad Request when I try to access a aspx-page running on
server 2003 SP1 from internet explorer 6 running on the same machine.

Here is the URL I am using:

http://www.myserver.com/20th-Century-Design/1900-talsdesign/Interior-design/Mid-century-modern/midcentury/Mid-century-design/midcentury-modern/Modern-Design/Modernism/Vintage-design/Img/508_1_632651758409835000/Arm-chair-Barbera-d'Argento-Designed-by-Paolo-Pallucco-for-Pallucco-Italia.aspx

If I reduce the length of the URL below 260 bytes, then I get a page
missing error (which is good, since it indicates that it passes through
whatever check is preventing it from working)

I get the impression that the aspx-engine never kicks in and that the 400
response is generated from within IIS. As far as I know an URL should be
able to be over 2k bytes.
I know that the URLScan utility (which is not installed) has a limitation
on the URL on 260 bytes...

the URL has been URL-Encoded (Server.URLEncode) so no invalid characters
should be in the URL. (I get the same error if I remove the '-character)

/Håkan

Oct 17 '06 #2
It is not a real path on the disk. I am using Context.RewritePath(), so the
path has nothing to do with the physical layout of the disk. The file
requested does not even exist as a physical file on the file system, and it
works fine as long as the request does not go over 260 bytes

/H

"bruce barker (sqlwork.com)" <b_*************************@sqlwork.comwrote
in message news:eR**************@TK2MSFTNGP05.phx.gbl...
long url's usually have long arguments. you are probably hitting limits on
the max length of a directory name or filename (255).

-- bruce (sqlwork.com)

"Håkan" <no***@nowhere.comwrote in message
news:u7**************@TK2MSFTNGP04.phx.gbl...
>Hi!

I get HTTP/1.1 400 Bad Request when I try to access a aspx-page running
on server 2003 SP1 from internet explorer 6 running on the same machine.

Here is the URL I am using:

http://www.myserver.com/20th-Century-Design/1900-talsdesign/Interior-design/Mid-century-modern/midcentury/Mid-century-design/midcentury-modern/Modern-Design/Modernism/Vintage-design/Img/508_1_632651758409835000/Arm-chair-Barbera-d'Argento-Designed-by-Paolo-Pallucco-for-Pallucco-Italia.aspx

If I reduce the length of the URL below 260 bytes, then I get a page
missing error (which is good, since it indicates that it passes through
whatever check is preventing it from working)

I get the impression that the aspx-engine never kicks in and that the 400
response is generated from within IIS. As far as I know an URL should be
able to be over 2k bytes.
I know that the URLScan utility (which is not installed) has a limitation
on the URL on 260 bytes...

the URL has been URL-Encoded (Server.URLEncode) so no invalid characters
should be in the URL. (I get the same error if I remove the '-character)

/Håkan


Oct 17 '06 #3
Check the metabase values for these settings:
AspMaxRequestEntityAllowed
MaxRequestEntityAllowed

And also check the registry key
HKLM/CurrentControlSet/Services/HTTP/Parameters
for these values:

MaxRequestBytes
UrlSegmentMaxLength
UrlSegmentMaxCount
MaxFieldLength

Mark

"Håkan" <no***@nowhere.comwrote in message
news:er*************@TK2MSFTNGP05.phx.gbl:
It is not a real path on the disk. I am using Context.RewritePath(), so
the
path has nothing to do with the physical layout of the disk. The file
requested does not even exist as a physical file on the file system, and
it
works fine as long as the request does not go over 260 bytes

/H

"bruce barker (sqlwork.com)" <b_*************************@sqlwork.com>
wrote
in message news:eR**************@TK2MSFTNGP05.phx.gbl...
long url's usually have long arguments. you are probably hitting
limits on
the max length of a directory name or filename (255).

-- bruce (sqlwork.com)

"Håkan" <no***@nowhere.comwrote in message
news:u7**************@TK2MSFTNGP04.phx.gbl...
Hi!

I get HTTP/1.1 400 Bad Request when I try to access a aspx-page
running
on server 2003 SP1 from internet explorer 6 running on the same
machine.
>
Here is the URL I am using:

http://www.myserver.com/20th-Century...n/Interior-des
ign/Mid-century-modern/midcentury/Mid-century-design/midcentury-modern/M
odern-Design/Modernism/Vintage-design/Img/508_1_632651758409835000/Arm-c
hair-Barbera-d'Argento-Designed-by-Paolo-Pallucco-for-Pallucco-Italia.as
px
>
If I reduce the length of the URL below 260 bytes, then I get a page
missing error (which is good, since it indicates that it passes
through
whatever check is preventing it from working)

I get the impression that the aspx-engine never kicks in and that the
400
response is generated from within IIS. As far as I know an URL should
be
able to be over 2k bytes.
I know that the URLScan utility (which is not installed) has a
limitation
on the URL on 260 bytes...

the URL has been URL-Encoded (Server.URLEncode) so no invalid
characters
should be in the URL. (I get the same error if I remove the
'-character)
>
/Håkan
Oct 17 '06 #4
Here are the values:

METABASE
AspMaxRequestEntityAllowed="204800"
MaxRequestEntityAllowed [Does not exist in the metabase]

REGISTRY
None of these parameters exist under the key:
HKLM/System/CurrentControlSet/Services/HTTP/Parameters

MaxRequestBytes
UrlSegmentMaxLength
UrlSegmentMaxCount
MaxFieldLength
Nothing of this seams to limit the URL to 260 bytes...

/H

"M. Burnett" <mb@xato.netwrote in message
news:Oh**************@TK2MSFTNGP02.phx.gbl...
Check the metabase values for these settings:
AspMaxRequestEntityAllowed
MaxRequestEntityAllowed

And also check the registry key
HKLM/CurrentControlSet/Services/HTTP/Parameters
for these values:

MaxRequestBytes
UrlSegmentMaxLength
UrlSegmentMaxCount
MaxFieldLength

Mark

"Håkan" <no***@nowhere.comwrote in message
news:er*************@TK2MSFTNGP05.phx.gbl:
>It is not a real path on the disk. I am using Context.RewritePath(), so
the
path has nothing to do with the physical layout of the disk. The file
requested does not even exist as a physical file on the file system, and
it
works fine as long as the request does not go over 260 bytes

/H

"bruce barker (sqlwork.com)" <b_*************************@sqlwork.com>
wrote
in message news:eR**************@TK2MSFTNGP05.phx.gbl...
long url's usually have long arguments. you are probably hitting
limits on
the max length of a directory name or filename (255).

-- bruce (sqlwork.com)

"Håkan" <no***@nowhere.comwrote in message
news:u7**************@TK2MSFTNGP04.phx.gbl...
>Hi!

I get HTTP/1.1 400 Bad Request when I try to access a aspx-page
running
>on server 2003 SP1 from internet explorer 6 running on the same
machine.
>>
Here is the URL I am using:

http://www.myserver.com/20th-Century...n/Interior-des
ign/Mid-century-modern/midcentury/Mid-century-design/midcentury-modern/M
odern-Design/Modernism/Vintage-design/Img/508_1_632651758409835000/Arm-c
hair-Barbera-d'Argento-Designed-by-Paolo-Pallucco-for-Pallucco-Italia.as
px
>>
If I reduce the length of the URL below 260 bytes, then I get a page
missing error (which is good, since it indicates that it passes
through
>whatever check is preventing it from working)

I get the impression that the aspx-engine never kicks in and that the
400
>response is generated from within IIS. As far as I know an URL should
be
>able to be over 2k bytes.
I know that the URLScan utility (which is not installed) has a
limitation
>on the URL on 260 bytes...

the URL has been URL-Encoded (Server.URLEncode) so no invalid
characters
>should be in the URL. (I get the same error if I remove the
'-character)
>>
/Håkan

>

Oct 17 '06 #5
There are various API's that have hard-coded path limits of 260 bytes.
It might just be that IIS is limiting the path based on the buffer
allocated for those API calls. It might just be easier to shorten your
paths.
Mark


"Håkan" <no***@nowhere.comwrote in message
news:ul**************@TK2MSFTNGP04.phx.gbl:
Here are the values:

METABASE
AspMaxRequestEntityAllowed="204800"
MaxRequestEntityAllowed [Does not exist in the metabase]

REGISTRY
None of these parameters exist under the key:
HKLM/System/CurrentControlSet/Services/HTTP/Parameters

MaxRequestBytes
UrlSegmentMaxLength
UrlSegmentMaxCount
MaxFieldLength
Nothing of this seams to limit the URL to 260 bytes...

/H

"M. Burnett" <mb@xato.netwrote in message
news:Oh**************@TK2MSFTNGP02.phx.gbl...
Check the metabase values for these settings:
AspMaxRequestEntityAllowed
MaxRequestEntityAllowed

And also check the registry key
HKLM/CurrentControlSet/Services/HTTP/Parameters
for these values:

MaxRequestBytes
UrlSegmentMaxLength
UrlSegmentMaxCount
MaxFieldLength

Mark

"Håkan" <no***@nowhere.comwrote in message
news:er*************@TK2MSFTNGP05.phx.gbl:
It is not a real path on the disk. I am using Context.RewritePath(),
so
the
path has nothing to do with the physical layout of the disk. The
file
requested does not even exist as a physical file on the file system,
and
it
works fine as long as the request does not go over 260 bytes

/H

"bruce barker (sqlwork.com)"
<b_*************************@sqlwork.com>
wrote
in message news:eR**************@TK2MSFTNGP05.phx.gbl...
long url's usually have long arguments. you are probably hitting
limits on
the max length of a directory name or filename (255).

-- bruce (sqlwork.com)

"Håkan" <no***@nowhere.comwrote in message
news:u7**************@TK2MSFTNGP04.phx.gbl...
Hi!

I get HTTP/1.1 400 Bad Request when I try to access a aspx-page
running
on server 2003 SP1 from internet explorer 6 running on the same
machine.
>
Here is the URL I am using:

>
http://www.myserver.com/20th-Century...n/Interior-des
>
ign/Mid-century-modern/midcentury/Mid-century-design/midcentury-modern/M
>
odern-Design/Modernism/Vintage-design/Img/508_1_632651758409835000/Arm-c
>
hair-Barbera-d'Argento-Designed-by-Paolo-Pallucco-for-Pallucco-Italia.as
px
>
If I reduce the length of the URL below 260 bytes, then I get a
page
missing error (which is good, since it indicates that it passes
through
whatever check is preventing it from working)

I get the impression that the aspx-engine never kicks in and that
the
400
response is generated from within IIS. As far as I know an URL
should
be
able to be over 2k bytes.
I know that the URLScan utility (which is not installed) has a
limitation
on the URL on 260 bytes...

the URL has been URL-Encoded (Server.URLEncode) so no invalid
characters
should be in the URL. (I get the same error if I remove the
'-character)
>
/Håkan


Oct 17 '06 #6
Hello All,

This is not an IIS limitation. It is an ASP.NET limitation (and ASPI.NET, I
believe, inherits it from the CLR.) Unfortunately, it is hard coded.

Thank you,
-Wade A. Hilmo,
-Microsoft

"M. Burnett" <mb@xato.netwrote in message
news:uc**************@TK2MSFTNGP03.phx.gbl...
There are various API's that have hard-coded path limits of 260 bytes.
It might just be that IIS is limiting the path based on the buffer
allocated for those API calls. It might just be easier to shorten your
paths.
Mark


"Håkan" <no***@nowhere.comwrote in message
news:ul**************@TK2MSFTNGP04.phx.gbl:
Here are the values:

METABASE
AspMaxRequestEntityAllowed="204800"
MaxRequestEntityAllowed [Does not exist in the metabase]

REGISTRY
None of these parameters exist under the key:
HKLM/System/CurrentControlSet/Services/HTTP/Parameters

MaxRequestBytes
UrlSegmentMaxLength
UrlSegmentMaxCount
MaxFieldLength
Nothing of this seams to limit the URL to 260 bytes...

/H

"M. Burnett" <mb@xato.netwrote in message
news:Oh**************@TK2MSFTNGP02.phx.gbl...
Check the metabase values for these settings:
AspMaxRequestEntityAllowed
MaxRequestEntityAllowed
>
And also check the registry key
HKLM/CurrentControlSet/Services/HTTP/Parameters
for these values:
>
MaxRequestBytes
UrlSegmentMaxLength
UrlSegmentMaxCount
MaxFieldLength
>
>
>
Mark
>
>
>
>
>
"Håkan" <no***@nowhere.comwrote in message
news:er*************@TK2MSFTNGP05.phx.gbl:
>
>It is not a real path on the disk. I am using Context.RewritePath(),
so
>the
>path has nothing to do with the physical layout of the disk. The
file
>requested does not even exist as a physical file on the file system,
and
>it
>works fine as long as the request does not go over 260 bytes
>>
>/H
>>
>"bruce barker (sqlwork.com)"
<b_*************************@sqlwork.com>
>wrote
>in message news:eR**************@TK2MSFTNGP05.phx.gbl...
>>
long url's usually have long arguments. you are probably hitting
>limits on
the max length of a directory name or filename (255).
>
-- bruce (sqlwork.com)
>
>
>
"Håkan" <no***@nowhere.comwrote in message
news:u7**************@TK2MSFTNGP04.phx.gbl...
>>
>Hi!
>>
>I get HTTP/1.1 400 Bad Request when I try to access a aspx-page
>running
>on server 2003 SP1 from internet explorer 6 running on the same
>machine.
>>
>Here is the URL I am using:
>>
>>
>>
http://www.myserver.com/20th-Century...n/Interior-des
>>
ign/Mid-century-modern/midcentury/Mid-century-design/midcentury-modern/M
>>
odern-Design/Modernism/Vintage-design/Img/508_1_632651758409835000/Arm-c
>>
hair-Barbera-d'Argento-Designed-by-Paolo-Pallucco-for-Pallucco-Italia.as
>px
>>
>If I reduce the length of the URL below 260 bytes, then I get a
page
>missing error (which is good, since it indicates that it passes
>through
>whatever check is preventing it from working)
>>
>I get the impression that the aspx-engine never kicks in and that
the
>400
>response is generated from within IIS. As far as I know an URL
should
>be
>able to be over 2k bytes.
>I know that the URLScan utility (which is not installed) has a
>limitation
>on the URL on 260 bytes...
>>
>the URL has been URL-Encoded (Server.URLEncode) so no invalid
>characters
>should be in the URL. (I get the same error if I remove the
>'-character)
>>
>/Håkan
>>
>
>>
>
>

Oct 18 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

8 posts views Thread by turnit \(removethis\) | last post: by
3 posts views Thread by Paul M | last post: by
3 posts views Thread by Stig-Arne Basberg | last post: by
2 posts views Thread by Kai Huener | last post: by
4 posts views Thread by Maximus | last post: by
3 posts views Thread by Eric | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.