How might one take user input from a web page that is not on a server (and thus has no server-side code) and do something with it?

why do you think that most web pages today require server-side programming
get and post method in html examples
overview of client/server programming on the web in html
html form
server-side scripting tutorial
multipart/form-data
server-side technologies
java server side programming

I have created an HTML form and I have got that part working. I am not sure, however, how to take that information and actually do something with it. This is for a school project so the page isn't accessible on the web. It is just stored on my machine. Thus, I have nothing happening on the server side of things. I have no experience working with php or SQL. I am comfortable with HTML, C#, and JavaScript, and I have experience with Python and Java; I am willing to learn whatever I need, however.

Ideally, what I want to happen is for the page to take the name that the user enters (lets say "John Doe") and navigate to another page based on that name (such as C:\JohnDoe). I have the first name and last name being requested separately, so the space between them won't be a problem.


Assuming that you will have an index.html file on the root folder, and then multiple users html files (ex: johndoe.html, janedoe.html, etc) alongside it in the same folder, you can write a javascript code just like this one. The downside is, you must create all html files beforehand, like ivan said, there's nothing you can do to dynamically create files needed using this script only.

<!DOCTYPE html>
<html>
  <head>
    <title>Homepage</title>
  </head>
  <body>
    <form>
      <input id="firstName" type="text" name="firstName">
      <input id="lastName" type="text" name="lastName">
      <input type="button" onclick="changePage()" value="Click Here">
    </form>
    <script type="text/javascript">
      function changePage() {
        const firstName = document.querySelector('#firstName').value
        const lastName = document.querySelector('#lastName').value
        const fileNameString = firstName+lastName
        window.location.href = fileNameString+'.html';
      }
    </script>
  </body>
</html>

Computer and Information Security Handbook, Because the code takes input from the user and executes it as part of an SQL statement One reason SQL injection is so devastating is that most of the time a Web has been tricked into performing SQL on behalf of the attacker, it does so in a is not maintained, an attacker will be able to execute code on the server in the  The server will also render pages to the client and process user input. Server-side processing happens when a page is first requested and when pages are posted back to the server. Examples of server-side processing are user validation, saving and retrieving data, and navigating to other pages. The disadvantage of server-side processing is the


The simplest way (imo) is to go ahead and make your local machine a "server" by installing nodejs, which you use by coding some javascript. W3Schools has a tutorial with examples. Your "server" will probably amount to just a few lines of javascript. There is an enormous library of tools to use, such as express, which makes it easy to implement a non-trivial server in short order. Many others. Be careful, though, you could get hooked.

ASP Made Simple, This means at times of heavy usage the web server may suffer severe performance problems. The ASP engine is somewhat more efficient and well-​written code ought to Though ASP produces plain HTML, there is no need to limit output to that. content to different devices, so that a PC user will get one type of web page,  This character is the string literal delimiter in SQL. If user input is submitted directly to the back-end server without sufficient validation or scrubbing, it then becomes incredibly easy to gain control of the DBMS. In order to test for this particular vulnerability, the hacker simply inserts something like. jo'hn


I'd say this might get you on some track, not exactly the best way to do it I'm sure, but some ideas due to the limitations you described. My idea would be saving the name on the input to localStorage or even a Cookie, and then just loading that data on the new page after a redirect. I don't know however if there's some way to 'create' the new page with the name dynamically.

function getUser() {
  var username = document.querySelector('#name').value;
  window.localStorage.setItem('name', username);
  window.location.href = "http://stackoverflow.com";
  console.log(username);
}
<input type="text" id="name">

<button type="button" id="nameBtn" onclick="getUser()">Send</button>

JavaScript: The Definitive Guide: The Definitive Guide, Client-side persistence is an easy way to give web applications a memory: a Cookies are also used for server-side scripting and are a standard extension to the scripts and server-side programs can use data that was input on one page on so server-side scripts can read and write * The name “cookie” does not have a  user uploads file via form input on web page ; Server-side logic stores the file ; In an Ajax cycle or a web page reload the server-side code identifies a fileName string to write in the div, "Here's what's currently uploaded" The file input may be re-presented too, so that the user is welcome to upload another file as well / instead.


Linux Server Security: Hack and Defend, As phishing attacks became more popular (where attackers trick users into went about completely rebranding a website, by injecting the necessary code to popular auction site and two banking websites had been cloned and used in phishing you can no longer expose queries to the outside via server-side languages,  Validating the client-side code makes sense even if your server-side code was not compromised. If an attacker is able to modify code or inject new code, he can easily capture credentials or modify the markup of the page and do phishing, and this is sufficiently severe for people to worry about.


The Internet Encyclopedia, Volume 3 (P, Although the wml code can do no processing, it can filter input so that only be done by sending the data back to a server or by embedding script in the page itself. not displayed for the user to see, but provide data for processing at the server. side does not produce the correct results, the document has been modified. It uses AngleSharp to parse, manipulate, and render HTML and CSS. HtmlSanitizer can be installed as a NuGet package, and the user input can be passed through relevant HTML or CSS sanitization methods, as applicable, on the server side. Please note that Sanitization as a security control should be considered only as a last option.


The Semantic Web Explained: The Technology and Mathematics behind , In the second, the URL contains an additional path /2007/04, which can be there is another option, using the so-called SSI (Server Side Include) feature. Web servers supporting SSI offer the opportunity to place specified directives into HTML the page (it must be noted that this is not typical; such counters are normally  The next PHP lines are a nifty way to dynamically alter page title names depending on what page the user is on. You have to manually input the pages and their accompanying page titles in the pages array. The code grabs the current page requsted by the user with REQUEST_URI, looks in the array and snags the appropriate title. Since the page