android - Issues with Caching on OkHttpClient 2.0 -


i have issue caching using okhttpclient 2.0. seems response ignoring cache-control header completely. how setting client , cache.

okhttpclient client = new okhttpclient(); cache = new cache(new file(session.getinstance().getcontext().getcachedir(),"http"), 10 * 1024 * 1024);  client.setcache(cache); client.setcookiehandler(cookiehandler.getdefault()); client.setconnecttimeout(connection_timeout, timeunit.milliseconds); client.setreadtimeout(socket_timeout, timeunit.milliseconds);

i believe cache directory created correctly. see in journal in /cache/http directory of application.

libcore.io.disklrucache 1 201105 2

this how creating request.

request mrequest =  new request.builder().url(murl).get().build();

getting response :

response response = client.newcall(mrequest).execute();

when using curl, headers as follows.

< http/1.1 200 ok < date: fri, 27 jun 2014 19:39:40 gmt * server apache-coyote/1.1 not blacklisted < server: apache-coyote/1.1 < cache-control: no-transform, max-age=1800 < content-type: application/json < transfer-encoding: chunked

the okhttp response headers follows.

connection:keep-alive content-type:application/json date:fri, 27 jun 2014 18:58:30 gmt keep-alive:timeout=5, max=100 okhttp-received-millis:1403895511337 okhttp-selected-protocol:http/1.1 okhttp-sent-millis:1403895511140 server:apache-coyote/1.1 transfer-encoding:chunked

the responses never cached , call client.getcache().gethitcount() gives 0. can please suggest changes might required here make cache work? thanks.

okay, problem , post requests using authorization bearer xxxx header , http://www.w3.org/protocols/rfc2616/rfc2616-sec14.html section 14.8 states these requests can't cached. solution use s-maxage on server instead of max age according :

when shared cache (see section 13.7) receives request containing authorization field, must not return corresponding response reply other request, unless 1 of following specific exceptions holds:

if response includes "s-maxage" cache-control directive, cache may use response in replying subsequent request.


Comments

Post a Comment

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

request animation frame stops working when exiting fullscreen clicking on original space's safari window. fine if fullscreen mode canceled escape key or calling cancelfullscreen(). steps reproduce: open https://dl.dropboxusercontent.com/u/769042/prezi/safari-fullscreen.html click "draw raf", kittie appears click "fullscreen", go fullscreen click "draw raf", kittie appears go space original safari was, showing "click exit fullscreen mode", click anywhere, out fullscreen click "draw raf", nothing happens what handling click calling: window.requestanimationframe(draw); which draws on canvas context: function draw() { ctx.drawimage(img, math.random()*500|0, math.random()*400|0, 100, 100); } i checked .hidden , .visibilitystate, updated correctly. tested on osx 10.9.3, safari 7.0.4 (9537.76.4). has workaround/solution other switching old settimeout? this sounds webkit bug 88940 : using reque...
Read more

jsf - How to ajax update an item in the footer of a PrimeFaces dataTable? -

this visual of table have: +---------+------------+-------------------+ | header1 | header2 | header3 | +---------+------------+-------------------+ | row | input | calc'ed output | | row b | input b | calc'ed output b | | etc.. | etc.. | etc.. | +---------+------------+-------------------+ | total: total calc'ed output | +------------------------------------------+ and stripped-down code: <p:datatable id="mytable" value="#{mybean.somelist}" var="currentitem"> <p:column headertext="header1"> <h:outputtext value="#{currentitem.name}" /> </p:column> <p:column headertext="header2"> <pe:inputnumber value="#{currentitem.inputval}"> <p:ajax event="change" listener="#{mybean.changelistener}" update="outputval outputtotal...
Read more

django - CSRF verification failed. Request aborted. CSRF cookie not set -

error: reason given failure: csrf cookie not set. in general, can occur when there genuine cross site request forgery, or when django's csrf mechanism has not been used correctly. post forms, need ensure: browser accepting cookies. view function uses requestcontext template, instead of context. in template, there {% csrf_token %} template tag inside each post form targets internal url. if not using csrfviewmiddleware, must use csrf_protect on views use csrf_token template tag, accept post data. you're seeing section of page because have debug = true in django settings file. change false, , initial error message displayed. can customize page using csrf_failure_view setting. did find, nothing helped, must foolish(( my template <form method="post">{% csrf_token %} {% field in form %} <div class="control-group"> {{ field }} </div> {% endfor %} <input type=...
Read more