Posted: 04 October 2005 at 1:21pm | IP Logged

For long urls like

http://xxx.yyyyyyyy.com/IndividualProduct~ProductID~77037~from~7~PID~95040~sel_255~0~selUnit_256~250~txtFrom_256~1~txtTo_256~100~selUnit_257~250~txtFrom_257~1~txtTo_257~100~selUnit_258~250~txtFrom_258~1~txtTo_258~100~selUnit_259~216~txtFrom_259~1~txtTo_259~100.html

I getting HTTP 400 - Bad Request.

Vlad Brook

Posted: 05 October 2005 at 3:28pm | IP Logged

Yaroslav,

It looks like in IIS 6.0 default settings for UrlSegmentMaxLength is 260.

I can increase it, but you are saying that it will not be crawled anyway.

Can you elaborate why?

Spacibo.

Vlad

Posted: 05 October 2005 at 9:18pm | IP Logged

Also if I'll restore "freezed" link to original form or with LinkFreeze disabled the very same link works without any problem so length should not be an issue. I've set UrlSegmentMaxLength to 1024, but it did not help so far.

SEO is a different story. This link most of the time is short, one or two params, but sometimes it became ugly long and I have no problem if it will be ignored by crawlers, but it fails for clients who have generated this long URL. It's rare, but happens. Is it possible to set some flags or else in URL to make Link Freeze to leave it as it is? Kind of inline disable for Link Freeze.

Spacibo.

Vlad

Posted: 06 October 2005 at 10:07am | IP Logged

I had to disable LinkFreeze on online pages in error. Without it works and it looks like:

http://tst.reedlink.com/IndividualProduct.aspx?ProductID=18820&KSPCProductId=18939&from=7&PID=77344&selUnit_261=687&txtFrom_261=1&txtTo_261=1000&txtFrom_260=1&txtTo_260=1000&selUnit_262=18&txtFrom_262=&txtTo_262=1000&selUnit_264=250&txtFrom_264=1&txtTo_264=10000&selUnit_265=250&txtFrom_265=1&txtTo_265=10000&

on dev site with LinkFreeze enabled it does not work(HTTP 400 - Bad Request) and looks like:

http://dev.reedlink.com/IndividualProduct~ProductID~18820~KSPCProductId~18939~from~7~PID~145128~selUnit_261~687~txtFrom_261~1~txtTo_261~1000~txtFrom_260~1~txtTo_260~1000~selUnit_262~18~txtFrom_262~~txtTo_262~~selUnit_264~250~txtFrom_264~1~txtTo_264~10000~selUnit_265~250~txtFrom_265~1~txtTo_265~10000~.html

if I'll remove some parameters from the same query, making it shorter it works:

http://dev.reedlink.com/IndividualProduct~ProductID~18820~from~7~PID~77225~selUnit_261~687~txtFrom_261~1~txtTo_261~1000~txtFrom_260~1~txtTo_260~1000~selUnit_262~18~txtFrom_262~~txtTo_262~1000~selUnit_264~250~txtTo_264~10000~selUnit_265~250~txtFrom_265~1~txtTo_265~10000~.html

Spacibo

Vlad

Posted: 07 October 2005 at 8:37am | IP Logged

Sure I've tryed that already, but it did not help. Also shorter URL with terminating & works fine. 

Is it possible to exclude some links on the page from beeing converted by LinkFreeze? say some attribute like <a linkfreeze="dissabled" href= "wery long URL not intended for SEO" >Foo</a>

Spacibo

Vlad

Posted: 08 October 2005 at 2:59pm | IP Logged

So, I'm back to original question: why long "Frozen" URL, see above, fails with Http 400?  Is there anybody else using LinkFreeze with a URL longer then 256 chars that does not have my problem?  May be not length, but number of parameters? Can you affirm that LinkFreeze" can handle href with length up to 512 and/or 32 parameters on IIS 6.0?

Also I was surprised to discover that LinkFreeze modifies action attribute of the form the same way as it does for href and POST fails with the same HTTP-400. I have 50 licenses for LinkFreeze and must to find some workaround.

Is it possible to use ReWrite to enable/disable links and/or action attribute?

Vlad

Posted: 17 October 2005 at 5:34pm | IP Logged

Hmm.  I tried already to add that Key with (default) value REG_SZ set to 0, restarted IIS , the same error

Do  you mean "UrlSegmentMaxLength" Key or value= dword:00000000  under the \Parameters key?

Spasibo.

Vlad

I also tried that before and no help either.

Posted: 18 October 2005 at 10:48am | IP Logged

I exported registry entry to .reg file to be sure that its what you recommend.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\UrlSegmentMaxLength]
@=dword:00000000

does not help so far

Vlad

Posted: 18 October 2005 at 5:10pm | IP Logged

I got it.  It's not a key "UrlSegmentMaxLength", but a value with this name under Parameters key. I set it to 512 and it works now for my ugly long URL.

Registry entry looks like that:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters]
"DisableServerHeader"=dword:00000001
"UrlSegmentMaxLength"=dword:00000200

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\SslBindingInfo]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\UrlAclInfo]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\Synchronize]

Spasibo.

Vlad