kbjradmin
New Member
- Messages
- 512
- Reaction score
- 2
- Points
- 0
i'm not quite sure if this is the right place to post this; if not, please just move it 
anyway, i recently decided to change over my http error handling from storing information in a hard-coded file to storing it in a database. i figured this might be helpful to someone else out there, so here is what i came up with: all of the http status codes, names, and descriptions in SQL format.
edit:
i don't know what happened to the file name, there . . .
it *was* tblHttpStatuses.sql.txt
anyway, i recently decided to change over my http error handling from storing information in a hard-coded file to storing it in a database. i figured this might be helpful to someone else out there, so here is what i came up with: all of the http status codes, names, and descriptions in SQL format.
edit:
i don't know what happened to the file name, there . . .
it *was* tblHttpStatuses.sql.txt
Last edited:
