Sandeep Kuttal wrote:
Hi Amos,
I am really sorry for my english since the sentence seemed ambiguous thats why
you interpreted it wrong. I am not optimizing the site. I just wanted to save
the contents of POST message and some GET messages.
Now I am really confused what you were talking about. I was asking what
your overall research aim was. You said PhD study, but we have no idea
the field yet.
> I choose to use a proxy server (squid) so that the software we are
going to develop is browser independent. But when I used squid I could
retrieve the contents of the GET message from it but not POST. So I
started looking for ways. I started with looking at squid archives and
downloaded squid 3.1.1 stable for getting the feel of the code. Squid
compiled and worked fine. Since some people suggested for ICAP/e-cap I
downloaded e-cap and then again squid 3.1.1 stable whole setup is
working fine with a problem that I cant see store.log. How to fix this
problem.
The cache_store_log option is still available in 3.1, its just been
turned to off by default. Add it back as before and things will be logged.
The eCAP adapter you are now trying has nothing to do with the store log
though. All body data passes through it and can be saved/retrieved from
a location of your choosing instead of in Squids' cache.
Other is the same big problem how to start for capturing POST messages. I just
want the contents inside the POST message to be saved. Kindly guide me how can
I achieve this target.
I'm not clued up on the internal eCAP workings myself yet. Maybe Alex or
Christos can point you at a better informatino source. I expect the eCAP
documentation to be the place to look.
Amos
On Apr 17, 2010, at 5:17 AM, Amos Jeffries wrote:
Sandeep Kuttal wrote:
Hi Amos,
Thanks for showing interest in my research. I am looking for
improving on a site for that I observed the data using httpfox i.e
extension of firefox to study data going and coming. After that I got
Ah, so what you are looking at is not in fact caching of POST data but how the
site needs to be optimized for reduced traffic?
to know that most of the important data intended for my research was
in POST messages both reply and request.
So for optimization the question there becomes: is POST the right request type
to be doing each of the actions?
GET, POST, PUT, and other request types each has a fixed set of defined
meanings. That defined meaning is also the reason why some requests can be
cached and some cannot.
In my experience as a website developer, I've seen many dynamic sites using
POST where they should be using GET.
So I intended on using a
cache server to capture the data and save it. The best cache server
out there is squid. So I went through the squid and found out that it
stores only GET message. I was looking for archives of squid to get a
view how to save the POST messages but till now got no success. According to
archives there are two solutions:
1) write a small ICAP servlet implementing this cache
This is the easy one for monitoring the data. It's relatively hard to identify
and pull things out of the squid cache.
2) * Modify how request entities are forwarded, temporarily
buffering the entity so you can process the request entity before the
request is forwarded. * Extend the public storeKey hashed data with
information as required to give each POST request/reply which should
be cached uniquely a unique storekey. * Remove the flag which makes
POST requests uncacheable (look for METHOD_POST).
Some body suggested me to look at ICAP/e-CAP and somebody suggested
to look at the second approach. So I am stuck how to start with. I
don't have any clue from where should I start. Kindly guide me
through this. Since this is the most important part of my research to
capture these POST messages.
Thanks Sandeep
On Apr 16, 2010, at 10:36 PM, Amos Jeffries wrote:
Sandeep Kuttal wrote:
Hi, I am a PhD student working on research for that I need to
cache the POST messages and I know no proxy server allows to
cache that. I want to work directly on it I can modify the squid
code some how and let it cache POST messages just for my research
since according to RFC the cache servers won't allow to cache
POST messages. Kindly subscribe me to your development list. Thanks, Sandeep
Greetings Sandeep,
Firstly welcome. It is always good to see someone new interested in
Squid.
I have some questions about your intended research;
What results you do see as being gained from this?
Have you read up on the reasons why the RFCs says POST cannot be
cached in shared proxies such as Squid? (the emphasis being on
*shared*)
Which part(s) of the POST->reply sequence do you see as being of
any use caching?
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.1
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.1
