MS Business Assessment SNAFU
-
Ran across this gem whilst performing the MS online business assessment for their partner program:
Do you host your own Web site or do you use a service provider?
<INPUT id=ctl00_cphMain_DynamicUIControl1_Field_cntl_88_rblInput_0 type=radio value=Yes name=ctl00$cphMain$DynamicUIControl1$Field_cntl_88$rblInput><LABEL for=ctl00_cphMain_DynamicUIControl1_Field_cntl_88_rblInput_0>Yes</LABEL> <INPUT id=ctl00_cphMain_DynamicUIControl1_Field_cntl_88_rblInput_1 type=radio CHECKED value=No name=ctl00$cphMain$DynamicUIControl1$Field_cntl_88$rblInput><LABEL for=ctl00_cphMain_DynamicUIControl1_Field_cntl_88_rblInput_1>No</LABEL> <INPUT id=ctl00_cphMain_DynamicUIControl1_Field_cntl_88_rblInput_2 type=radio value="Don't Know" name=ctl00$cphMain$DynamicUIControl1$Field_cntl_88$rblInput><LABEL for=ctl00_cphMain_DynamicUIControl1_Field_cntl_88_rblInput_2>Don't Know</LABEL>
-
It makes sense with Boolean logic. Why, yes, I do ( host_my_own_website || use_a_service_provider ). They even provided a FILE_NOT_FOUND response.
-
good stuff - forgot about the logic angle on things. makes perfect sense now!
-
This may make sense for employees of big companies who don't know how their IT department is handling things.
-
@TheRider said:
This may make sense for employees of big companies who don't know how their IT department is handling things.
So which option would you choose if you use a service provider?
-
@shakin said:
"Don't know" of course :P@TheRider said:
This may make sense for employees of big companies who don't know how their IT department is handling things.
So which option would you choose if you use a service provider?
Ok, you got me there. I didn't read the question well enough...
-
@pauluskc said:
Ran across this gem whilst performing the MS online business assessment for their partner program:
Do you host your own Web site or do you use a service provider?
<input id="ctl00_cphMain_DynamicUIControl1_Field_cntl_88_rblInput_0" value="Yes" name="ctl00$cphMain$DynamicUIControl1$Field_cntl_88$rblInput" type="radio"><label for="ctl00_cphMain_DynamicUIControl1_Field_cntl_88_rblInput_0">Yes</label> <input id="ctl00_cphMain_DynamicUIControl1_Field_cntl_88_rblInput_1" checked="checked" value="No" name="ctl00$cphMain$DynamicUIControl1$Field_cntl_88$rblInput" type="radio"><label for="ctl00_cphMain_DynamicUIControl1_Field_cntl_88_rblInput_1">No</label> <input id="ctl00_cphMain_DynamicUIControl1_Field_cntl_88_rblInput_2" value="Don't Know" name="ctl00$cphMain$DynamicUIControl1$Field_cntl_88$rblInput" type="radio"><label for="ctl00_cphMain_DynamicUIControl1_Field_cntl_88_rblInput_2">Don't Know</label> answer matrix is simple
Host own website -> yes
use service provider -> yes
work in centrafrica without internet connection -> no
don't own a PC and too lazy to ask it if we have net presencee -> don't know
conclusion: they just want to know if you are on the net, not how you are on it.
-
@tchize said:
That 519 byte URL yields a:
Bad Request (Invalid URL)
error. Nice.
And it obviously wreaks havoc on the page layout.
-
Severe tag abuse breaks TDWTF
@merreborn said:
@tchize said:
That 519 byte URL yields a:
Bad Request (Invalid URL)
error. Nice.
And it obviously wreaks havoc on the page layout.
well...didnt you know...windows wont accept any file or web addresses with more than 256 charecters in the entire path & filename. & yes, it does wreck havoc with page layout.
-
@Steeldragon said:
well...didnt you know...windows wont accept any file or web addresses with more than 256 charecters in the entire path & filename. & yes, it does wreck havoc with page layout.
Actually, Windows accepts them just fine. It's Explorer itself (and IE, since they're basically the same thing) that has the 256-character limited buffer.
Yes, this means that you can create files which Explorer cannot handle. Any application which uses a dynamic buffer and the correct API calls can do so. Best of all, Explorer lacks any sanity checking on local filesystem paths, so it will actually overrun that buffer and crash when confronted with a longer path.
-
Someone is really asking for a frontpage article here ;-)
This "bad request" response obviously comes from the server and is not client-generated ( if you check the headers you'll even see it's a generic error status 400 ). It's generated either by the server or probably by the "community server" application itself, which may have a limit on tag size.
As for the path itself, it does not depend on filesystem limitations on [url=http://en.wikipedia.org/wiki/Comparison_of_file_systems#Limits]filename/path length[/url].
Maximum length in url varies depending the browser, see [url=http://classicasp.aspfaq.com/forms/what-is-the-limit-on-querystring/get/url-parameters.html]URL length limits[/url]. The standard limit is 1024, while most browsers accept more than 2000 characters ( yes, even IE since 4.0+ )
-
@aikii said:
Maximum length in url varies depending the browser, see [url=http://classicasp.aspfaq.com/forms/what-is-the-limit-on-querystring/get/url-parameters.html]URL length limits[/url]. The standard limit is 1024, while most browsers accept more than 2000 characters ( yes, even IE since 4.0+ )
Bizarrely enough, Explorer has the 256-character limit specifically on file URLs/paths (even though all filesystems supported by windows can have longer paths). That's not related to the overall URL length limit.
-
@asuffield said:
@Steeldragon said:
well...didnt you know...windows wont accept any file or web addresses with more than 256 charecters in the entire path & filename. & yes, it does wreck havoc with page layout.
Actually, Windows accepts them just fine. It's Explorer itself (and IE, since they're basically the same thing) that has the 256-character limited buffer.
Yes, this means that you can create files which Explorer cannot handle. Any application which uses a dynamic buffer and the correct API calls can do so. Best of all, Explorer lacks any sanity checking on local filesystem paths, so it will actually overrun that buffer and crash when confronted with a longer path.
Well, technically it's the standard Windows API calls for accessing files that have that limitation - there are ways of accessing files with long paths, but they have some caveats attached IIRC.
-
@makomk said:
Well, technically it's the standard Windows API calls for accessing files that have that limitation - there are ways of accessing files with long paths, but they have some caveats attached IIRC.
The caveat is that Explorer doesn't use them, so if you use them, you'll end up creating files that will crash Explorer. Same thing I'm talking about.
