Shawn O. Pearce ac6cda955c Ensure all smart HTTP errors are sent to clients ... Error messages are typically short, below the 32 KiB in-memory buffer size of the SmartOutputStream. When an error is queued up for sending to a client and an exception is thrown up into the servlet handler we discarded the message and sent nothing to the client, as the messages were stuck inside of the SmartOutputStream buffer. Hoist the creation of the output stream above the invocation of try block of the service, and use close() in the few catch blocks that assume there are buffered messages ready for transmission. This will ensure errors from unpacking a stream in ReceivePack are sent off to a client correctly, as previously these were causing no status report to arrive at the client side as the data was stuck in the buffer. Change-Id: I5534b560697731121f48979ae077aa7c95b8e39c		2011-12-01 16:01:11 -08:00
..
server	smart-http: Fix recognition of gzip encoding	2011-02-15 16:32:51 -08:00
test	Ensure all smart HTTP errors are sent to clients	2011-12-01 16:01:11 -08:00