webmachine / src / webmachine_request.erl

Author Commit Message Labels Comments Date
Ryan Tilder
An interim fix for PUT request bodies greater than 64M
tell mochiweb we recv body
update version and quip
Bryan Fink
the number of crlf on 100-continue shall be 2, and 2 shall be the number of crlf (thanks, marc)
Bryan Fink
bug fix: expect {Answer, ReqState} from webmachine_request:req_cookie/0 and :req_qs/0, not just Answer
put incoming req_body in process dict (there is really no other decent way to allow more than one call to wrq:req_body in the same resource fun anymore)
move body-fetched-yet test to outer state from reqdata also change record name so as to be able to make all modules using the reqstate record recompile to see the new record def.
trim the reqdata/reqstate loop in tracebacks
quip update
error catching here does not help
Paul J. Davis
Added a Write callable response method. Body producing functions can return {writer, fun my_callable/1} as the status to indicate that they would like a fun write/1 callable passed to that function. This callable can then be used to write data to the client. An example: -module(writefun_resource). -export([init/1, to_html/2]). -include_lib("webmachine/include/webmachine.hrl"). init([]) -> {ok, undefined}. to_htm…
removal of the request_srv process
Bryan Fink
host-based dispatching dispatch rules can now take two different forms: The old form: {PathMatchSpec, Module, Paramters} The new form: {HostMatchSpec, [{PathMatchSpec, Module, Parameters}]} The former is equivalent to the latter with HostMatchSpec={['*'],'*'} HostMatchSpec is matched against one of (in order of preference): X-Forwarded-For, X-Forwarded-Host, X-Forwarded-Server, Host HostMatchSpec can have two form…
provide and honor wrq:set_max_recv_body/2
streaming API for request body
only fetch body off socket when requested, not when initializing
cleaner set of final resp body
initial import