M
Mark Schupp
It is the fault of the code.
The code does something *wrong* (it is illegal under IIS/ASP to try to
output headers after content has been output) if the user has cookies
disabled.
Depending on the application, it may or may not be serious enough to worry
about but it is a programming logic error.
The code does something *wrong* (it is illegal under IIS/ASP to try to
output headers after content has been output) if the user has cookies
disabled.
Depending on the application, it may or may not be serious enough to worry
about but it is a programming logic error.