Since libapreq has been integrated into mod_wxjs. Original settings (whatever that was) for libapreq should be same as previous mod_wxjs version or else needs to be documented (as new mod_wxjs settings). Otherwise people migrating from version<0.974 will have their http requests break.
Message thread below.
Aug 20, 1:00 pm
I checked source, and founds this in mod_wxjs_handler.cpp
620: AP_INIT_TAKE1("APREQ2_ReadLimit", (cmd_func)
apreq_set_read_limit, NULL, OR_ALL,
"Maximum amount of data that will be fed into a
parser."),
So I put APREQ2_ReadLimit 1K in conf and now the request.post problem
is gone. By the way, I plan to upload files, does this limit the
upload size or just the parameter parsing size? If I remember
correctly the files goes straight to the Brigade? So do I need to set
the BrigadeLimit for file upload scripts?
I didn't find this in 0.9.72 source. (actually I notice a significant
amount of change in the mod_wxjs between 0.9.72 and 0.9.74?)
I guess people should be aware of below new settings:
APREQ2_TempDir
APREQ2_ReadLimit
APREQ2_BrigadeLimit
Curious what these do:
wxJS_ReportErrorOnPage
wxJS_AuthScript
Reply:
I've integrated libapreq into mod_wxjs so we don't need to load those
additional modules anymore.
I'll change those APREQ2 settings into mod_wxjs versions. I do wonder
why this worked in the previous release. Maybe it is some initial value
that is not set.
wxJS_ReportErrorOnPage will report a javascript error on the webpage
when you set it to Y or y. wxJS_AuthScript is not used yet.
Franky.
