> May I ask how you determined what action to take on the submit?

I looked at the action specified in the < form > tag of the page that I was submitting.

I took a quick look at the page that you are working on. It seems that the button calls a javascript function called navigate that is defined on their "common.js" file.

You can download their javascript file from https://fortress.wa.gov/dol/ddl/dsd/Inc/common.js and take a look at what the navigate function does.

The navigate function seems call the validatefields function defined on the page which in turn sets the values of two hidden fields and then submit the page to the server. I imagine that once the page is posted back the server notices the values of these hidden fields and does some extra processing (e.g. validate the license and redirect you to a different page to display the results of the validation.)


>The problem I'm having is the buttons don't just obviously
> naviage to a page.

You are right, it seems that they post back this same form and then the server decides to navigate to a different form based on the values of the hidden fields.


> The page that you end up on if you
> click through won't allow a direct hit.

That's usually the case. I've found that most of the times is better to hit the page that users hit and just emulate all the values that a user would enter so that the request looks exactly like if a person actually hit the page.