network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 4 months |
| seen | Dec 17 '12 at 18:34 | |
| stats | profile views | 2 |
|
Mar 22 |
comment |
IIS and content caching I do like that link you just gave me... after I posted the question, I thought something with url rewrites might just work. I'll have to sleep over it. |
|
Mar 22 |
awarded | Scholar |
|
Mar 22 |
accepted | IIS and content caching |
|
Mar 22 |
awarded | Student |
|
Mar 22 |
comment |
IIS and content caching I'll admit, this would work, but that's just ... it would be very intractable to manage, complicates the use of a source code control system, and likely somebody's just going to mess up somewhere. A few years back, I dealt with the (potential) issue on a different by appending a query string built off some random number internally generated by the last build, and it did work (I don't recall that we ever had any issues), but it was still a pain to manage. It's "fixes" like these which I'm trying to avoid. |
|
Mar 22 |
asked | IIS and content caching |
|
Mar 22 |
awarded | Supporter |
