It still depends on apache configs.. you can confiure how much the access log puts out regarding that in LogLevel or LogFormat directive.. see the docs for more details.
a good place to start if you are really concerned: http://httpd.apache.org/docs/2.2/mod/mod_log_config.html#logformat On Aug 12, 3:14 pm, Stephan Beal <sgb...@googlemail.com> wrote: > On Aug 12, 8:22 pm, "Michael Geary" <m...@mg.to> wrote: > > > > on the server side, i personally recommend using the json2.js > > > API (i.e. JSON.parse() and JSON.stringify()) over > > > $.getJSON(). getJSON uses an HTTP GET, which is very rude > > > vis-a-vis Apache logs (because all your JSON gets logged > > > there in urlencoded form). > > > No, that's wrong. Yes, $.getJSON() does do a GET, but that has no effect at > > all on the *download* format, which is what Mark is asking about given his > > use of json_encode. > > It's not wrong, but it could have been worded better. First, i wrote > "server side" instead of "client side", which is just downright wrong. > i wasn't referring to the download format, but to the type of request. > Requests *always* come from the client, so the direction of the > exchange was implicit (to the server as opposed to from the server). > > > Your downloaded JSON data will not show up in any Apache logs (unless, I > > suppose, if you have some kind of ultra-verbose logging turned on that logs > > i didn't mean to imply that it would. i was only referring to the GET > parameters sent from the client. Those get logged.
