|
>The only difference being the variable name, MR# vs MRNbr. I agree that it's >probably the HTTP server. If I use the variable name MR# in a form, >Net.Data sees the value; but if I use it in a URL as above, Net.Data does >not see the value. Hi Peter, was the form using method GET or method POST? I guess it was using POST - otherwise the same problem should have appeared as i understand it. # says that everything after it is the name of an anchor on the target page. At least it appears so due to the behaviour. *checking* ftp://ftp.isi.edu/in-notes/rfc2396.txt <cite>4.1. Fragment Identifier When a URI reference is used to perform a retrieval action on the identified resource, the optional fragment identifier, separated from the URI by a crosshatch ("#") character, consists of additional reference information to be interpreted by the user agent after the retrieval action has been successfully completed. As such, it is not part of a URI, but is often used in conjunction with a URI. </cite> OK, everything clear, it works as designed. Conclusio: Don't use forbidden characters for variable names (at least when using method GET). Thanks! best regards / Mit freundlichen Grüssen Anton Gombkötö Avenum Technologie GmbH http://www.avenum.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.