Requests from from a browser or any other suitable socket based
mechanism that sends requests.  Servlets and servers don't send
requests, although you can have a client in a server that does send
requests.  You could, I suppose, even build a request making mechanism
inside a servlet or as a field for a servlet.  But, that does not mean
the servlet is making the request qua Servlet.  Servlets handle
requests and return responses.  Responses are not requests.  Responses
tend to be HTML and requests are name value pairs and streams.

On 5/18/05, Michael Mehrle <[EMAIL PROTECTED]> wrote:
> Simple question, but it's driving me nuts. I really don't want to get into
> the whole web service business - all I need is for a servlet to be the
> recipient of its own request. Or - in other words - can a servlet act like a
> web browser - just without the GUI?
> 
> Use case:
> 
> - Servlet issues https request to an outside server (via
> getServletContext().getRequestDispatcher(https://www.someoutsideserver/) )
> - Outside server processes request and responds with POST response (also via
> https).
> - Servlet [somehow] is able to be the recipient of the response.
> - Servlet parses the response and stores data to the database.
> 
> Notes:
> 
> - The servlet is not the default servlet on that tomcat instance.
> - Everything happens via https and I expect the outside server will listen
> on 443 and tomcat on 8443
> 
> ANY suggestions would be very helpful - this seems to be a tricky one.
> 
> TIA,
> 
> Michael
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


-- 
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to