HTML Form: why action can't have get value in it?

Question

When i try the following structure, it does't send id=value

<form action="some.php?id=value" method="get">
   <input name="name1" value="value1">
   <input type="submit">
</form>

I know that i can send id=value in hidden field, but it's interesting, why it doesn't allow such structure?

Solution 1

It's because the "method=get" section of the form implies that the query values have to come from the form values.

The collection which contains "id=value" is overidden by the collection containing the form values.

This behaviour seems to be built into each browser, so I expect that it's part of the HTML specification.

Update

Ahah:

This has been asked before: submitting a GET form with query string params and hidden params disappear

To Quote:

As the specifications (RFC1866, page 46; HTML 4.x section 17.13.3) state:

If the method is "get" and the action is an HTTP URI, the user agent takes the value of action, appends a `?' to it, then appends the form data set, encoded using the "application/x-www-form-urlencoded" content type.

Solution 2

If your form method is POST, then you will not see id as part of the POSTed values, you can use the QueryString collection to access it.

Solution 3

Isn't it because this would send a request to

some.php?id=vaule?name1=value1

instead of

some.php?id=vaule&name1=value1 ?

As far as I know a query string only has one "?" and a "?" is appended to the URL when you use GET parameters.

Comments

[Simon]

i want to send some fields with get, at the same time i don't want to lose the current value of my get variables. for example if now i'm in some.php?lang=am after submiting i need to redirect to some.php?lang=am&fild1_name=field1_value...

[Austin Fitzpatrick]

You can't bookmark a POSTed page though. Perhaps he wants a search function where people could bookmark the results, or something similar.

[Lèse majesté]

You could have collisions either way. It's just as easy to create two inputs with the same name. The least astonishing behavior would be to allow parameters in the URL and simply overwrite them if an input with the same name exists.

[GreenMatt]

Actually, it's not correct; as the if=value part is not sent. See Seanyboy's answer or mine.

[Krisztián Balla]

What if you have 100 parameters? You would need to add 100 such if statements.

[Kiquenet]

What is UrlHelperExtensions.CreateRequestAgnosticUrlHelper ?

[Krisztián Balla]

@Kiquenet: Unfortunately I no longer have access to this code. If I recall correctly the method creates an UrlHelper object that does not include parameters from the current request.