|Re: HTTP request after server startup [message #838079 is a reply to message #828062]
||Fri, 06 April 2012 14:36
| Larry Isaacs
Registered: July 2009
On 3/24/2012 2:05 AM, Brett Randall wrote:|
> Thanks Larry.
> My interest here is when testing a webapp, and one is interested in
> observing behaviour on the very first request to the application, and
> having control over that request - parameters etc.
> I take it that the request is currently a hard-coded GET to http
> ://<hostname>:<port>/ ? Would it be feasible to open this to end-user
> configuration? I appreciate that it might be difficult to allow it to be
> turned-off altogether, as to your point WTP won't know when the server
> has finished loading. But my tests for Tomcat at least suggest that I
> can send a request such as GET /foo/bar and expect a 404, and the 404
> will only be delivered once the server is fully-started.
> So if I was able to configure/customise the ping URL, and perhaps
> convince WTP to accept a 404 (not sure what it does with status codes
> now), then this would help with the above requirement. Aside: the
> current test-request does follow 301 redirects.
> Does this have a chance of gaining support as an enhancement request?
Sorry to take so long to respond. I believe the current behavior is to
simply wait for a connection. I don't think it currently checks the
response in any way. You are welcome to enter a Bugzilla enhancement
request. Since my cycles available for WTP these days are pretty
limited, it would very likely need a patch to get the feature added.
Default behavior would be the same as the current behavior.
Powered by FUDForum
. Page generated in 0.02370 seconds