Ryo, That must be correct behavior. W3C says :
http://www.w3.org/Protocols/HTTP/HTRESP.html '500' means 'Internal Error'. Unless the JMeter designers intended to give you complete latitute to interpret response codes (and I don't think they do) , this must be the intended behavior. Lee Peterson SAS Institute, Inc. SAS ... The Power to Know > -----Original Message----- > From: Ryo Sode [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 15, 2004 6:45 PM > To: JMeter Users List > Subject: HTTP Status Code 500? > > > Hi, > > I have come across a behavior which I am having hard time > deciding whether > it's a bug or an intentional behavior. > > When a JMeter HTTP sampler with a Response Assertion makes a > request and the > HTTP status code in the server response is 500 (i.e. > Unexpected error) no > matter what kind of Response Assertion I setup, (e.g. > Response Code = 500 or > Response body = Unexpected Error) the test always comes out > to be fail. > > Can someone tell me if this is the correct behavior or if > this is a bug? > Thanks. > > Ryo > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
