5 ms·

Best I could do on a freshly installed Win2k12 with IIS was: curl -v http://server-name/iis-85.png http://server-name/iis-85.png -H "Range: bytes=18-1844674407

by davman 11y ago

Best I could do on a freshly installed Win2k12 with IIS was: curl -v http://server-name/iis-85.png http://server-name/iis-85.png -H "Range: bytes=18-18446744073709551615" Run the curl twice and the bluescreen happens the second time. If I don't request the image then it doesn't work. I've not added any specific rules for output caching. Edit: The crash screen is very dull: http://imgur.com/MZ7VNHQ http://imgur.com/MZ7VNHQ

endian01 11y ago
Confirmed with Windows 8.1 Pro w/ IIS .. Same conditions, must run request twice for the .png (with the IIS rule set) Not like it matters, but I am toying with the first Range number.. (ie: 40-1884...615) Edit: crash @ 40-1884, oh-shit-reboot at 100-1884
- Satchelmouth 11y ago
  Confirmed: I couldn't force a BS using the originally supplied range numbers, but changing it as per above to 100 did the trick (windows 2008 non R2 & 2012 R2)
Khao 11y ago
Did you have to configure any rule in the Output Caching or that's completely default values?
- davman 11y ago
  I initially configured rules (I was following your instructions) but I've now deleted the rules and still have the crash.
  - Khao 11y ago
    Damnit. I'll double-check on my side too and update my answer accordingly. I don't want people to think they're safe if they're not!
  - artanis0 11y ago
    Can confirm. No Output Caching rules defined, I am still able to reproduce crash. [EDIT] What is handy is that it appears that disabling "Enable kernel cache" takes effect immediately. No iisreset or server reboot required in my testing environment.
    - davman 11y ago
      Yes, unticking that checkbox works for me instantly.
davman 11y ago
What is also interesting is that if I do this instead: curl -v http://10.243.0.221/iis-85.png http://10.243.0.221/iis-85.png -I -H "Range: bytes=18-18446744073709551615" (added -I), then it doesn't cause the crash.
- gkop 11y ago
  -I sends a HEAD rather than a GET, so that's not too surprising.
  - davman 11y ago
    Ahh yeah, that should have been obvious. Thanks!
shawnz 11y ago
> Edit: The crash screen is very dull: Could you show the event log entry also?
- davman 11y ago
  I couldn't find anything that wasn't just the report of a bluescreen.
functionCall 11y ago
http://imgur.com/RTbw7co http://imgur.com/RTbw7co confirmed for default IIS without any rules set, completely default values.
Rapzid 11y ago
Yup, took me a few more goes but confirmed 2012R2 on AWS behind ELB. I've been up for a while making new images.. 5:08AM :| I can also confirm it crashes my command window using curl via cygwin lol.

by davman 11y ago

endian01 11y ago

Confirmed with Windows 8.1 Pro w/ IIS .. Same conditions, must run request twice for the .png (with the IIS rule set) Not like it matters, but I am toying with the first Range number.. (ie: 40-1884...615) Edit: crash @ 40-1884, oh-shit-reboot at 100-1884

Satchelmouth 11y ago
Confirmed: I couldn't force a BS using the originally supplied range numbers, but changing it as per above to 100 did the trick (windows 2008 non R2 & 2012 R2)

Khao 11y ago

Did you have to configure any rule in the Output Caching or that's completely default values?

davman 11y ago
I initially configured rules (I was following your instructions) but I've now deleted the rules and still have the crash.
- Khao 11y ago
  Damnit. I'll double-check on my side too and update my answer accordingly. I don't want people to think they're safe if they're not!
- artanis0 11y ago
  Can confirm. No Output Caching rules defined, I am still able to reproduce crash. [EDIT] What is handy is that it appears that disabling "Enable kernel cache" takes effect immediately. No iisreset or server reboot required in my testing environment.
  - davman 11y ago
    Yes, unticking that checkbox works for me instantly.

davman 11y ago

What is also interesting is that if I do this instead: curl -v http://10.243.0.221/iis-85.png http://10.243.0.221/iis-85.png -I -H "Range: bytes=18-18446744073709551615" (added -I), then it doesn't cause the crash.

gkop 11y ago
-I sends a HEAD rather than a GET, so that's not too surprising.
- davman 11y ago
  Ahh yeah, that should have been obvious. Thanks!

shawnz 11y ago

> Edit: The crash screen is very dull: Could you show the event log entry also?

davman 11y ago
I couldn't find anything that wasn't just the report of a bluescreen.

functionCall 11y ago

http://imgur.com/RTbw7co http://imgur.com/RTbw7co confirmed for default IIS without any rules set, completely default values.

Rapzid 11y ago

Yup, took me a few more goes but confirmed 2012R2 on AWS behind ELB. I've been up for a while making new images.. 5:08AM :| I can also confirm it crashes my command window using curl via cygwin lol.