title: J2EE Solution for implementing Proxy-Server: monitoring , tracking , saving and (reloading) Http Traffic
body: <p>As the title describes a Proxy should be implemented to monitor, track , save and (reloading) the Http Traffic of the outgoing requests incoming responses of client.</p>
  
  <p>I am in the Design/Analysis phase: Here is the process flow:</p>
  
  <ol>
  <li>Client set his request URL (the target) through a  proxy-page on the proxy (i.e: <a href="http://localhost:port_name/proxy_confg_page.html" rel="nofollow">http://localhost:port_name/proxy_confg_page.html</a>).</li>
  <li><p>The client send a (POST/GET/etc. method) request through the proxy(at if the proxy would send it). The proxy sniffs the traffic, saving the request parameter anyhow. </p></li>
  <li><p>the proxy receives the (HTTP) response from the requested URL (target URL).</p></li>
  <li>For successful requests (Response Status code between 200-299), the proxy can save both the request and the response somehow for further processes and redirect the response to the client him to "see" its answers. </li>
  <li>the client receives the incoming (http) response from the proxy and displays it.</li>
  <li>the client might then click a link the response, setting it to be the next target URL for the next request, through the proxy</li>
  <li>and it start all over from the beginning at step 1</li>
  </ol>
  
  <p>i have 2 questions:</p>
  
  <ul>
  <li><p>is the process flow decribed above logical stable ? if not would'nt you mind please to correct me? </p></li>
  <li><p>i want to use a solid and scalable lib to process the traffic (read, update) in the proxy : i think of HttpClient. can it please do the job ? if not thank you to tell me why and which alternative might be better.</p></li>
  </ul>
  
  <p>i hope to hear some good answers from some experienced Web-developers. Thank you  </p>