From 5aece2300e0f6f1b41a9a8b2164126dd44f821aa Mon Sep 17 00:00:00 2001 From: wcrisman Date: Mon, 29 Dec 2014 09:24:51 -0800 Subject: [PATCH] Finished fixing the bug in the last two commits where by the content filling the buffer was causing major problems with the resulting client display (not sure why and don't care). --- .../com/foundation/web/server/HttpMessageBuffer.java | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/Foundation Web Core/src/com/foundation/web/server/HttpMessageBuffer.java b/Foundation Web Core/src/com/foundation/web/server/HttpMessageBuffer.java index bc57820..239bbf9 100644 --- a/Foundation Web Core/src/com/foundation/web/server/HttpMessageBuffer.java +++ b/Foundation Web Core/src/com/foundation/web/server/HttpMessageBuffer.java @@ -304,24 +304,12 @@ private void prepareResponse(Response response) { Debug.log(ch.toString()); }//if// - //Ignore the content if we are only accessing the header.// -// if(content != null && request.getRequestType() != Request.TYPE_HEAD) { -// content.get(buffer); -// }//if// - //Save the buffer as the current pending outbound message for this socket context.// - //currentOutboundMessage = new MessageBuffer(buffer, response, content != null && request.getRequestType() != Request.TYPE_HEAD ? content : null); -// queueOutboundClientMessage(new MessageBuffer(buffer, response, content != null && request.getRequestType() != Request.TYPE_HEAD ? content : null)); setBuffer(buffer); if(content != null && request.getRequestType() != Request.TYPE_HEAD) { this.content = content; }//if// - - //Fill the remaining buffer space with the content.// - if(this.content != null) { - this.content.get(buffer); - }//if// }//try// catch(Throwable e) { Debug.log("Fatal Error: Failed to build and send the response message due to an exception.", e);