comment-Check HTTP result header-1

For most pages you expect response codes below 400, typically 200. Therefore the default handling fails with codes over or equal 400.

In order to check that your resource is protected as expected you would need to write a custom step (maybe subclassing "Invoke").

4 comments (by Shaun Davis, Mittie, Bob83, Boy11) | post comment

labels

attachments

Created by admin. Last edited by admin, 5 years and 223 days ago. Viewed 1,068 times. #2

[diff] [history] [edit] [rdf]

Shaun Davis, 330 days ago.

Hey just a heads up, I wanted to let everyone know that Xio Dibin speaks English. I hope I posted in the right location?

I advise you send questions to our mailinglist at webtest@lists.canoo.com. You will have much more better chance of getting an answer.

Success has a smell, a flavor, a feel. ,

For some folks I know, it is an irrepressible and damnable urge. ,

Registration
Want to contribute? You can register here.

Help
For hints about formatting text see snipsnap-help.

Entry Points:

Editor's Pick:

Logged in Users: (0)

… and 2 Guests.

Recently Changed

weblogsping (Red20)
comment-Check HTTP result header-1 (Bob83)
interwiki (Stinky96)
weblogsping (Miss59)
weblogsping (Miss59)
comment-Check HTTP result header-1 (Boy11)
interwiki (JXL100)
interwiki (RDcp1EIPAC)
recent-changes: null
more Recent Changes...
RSS News Feed:

Powered by SnipSnap 1.0b1-uttoxeter