I have a website on a pro package with Geocities. On my form after the user subbmits an entry a defult whicte screen comes up saying

The following form submission was sent.

Name:
Telephone Number:
Country:
Email Address:
Messeage:

I don't like this because it means the user is directed away from my site and the url is a geocities url, not the url of my site.

I can change the page to any page i want but i want to also have the details that the user typed in that page.

Any one know what to do?

Dani AI

Generated

Short summary for : to keep visitors on your own URL and show the submitted values you need either control of the form processor (server-side script) or a client-side/third‑party workaround. is correct that a custom script on the server is the cleanest fix; ’s meta-refresh is a simple fallback but won’t carry the user’s form data to a custom page.

Easiest, low-effort option: use a hosted form processor that accepts POSTs from a static page and then redirects back to a thank-you page on your site. Many services let you set a redirect URL (or configure it in form settings) so the visitor ends up on your URL after submission. Example (Formsubmit style):

<form action="https://formsubmit.io/send/YOUR_CODE" method="POST">
<input type="hidden" name="_redirect" value="">
<input name="name" />
<input name="email" />
<textarea name="message"></textarea>
<input type="submit" value="Send">
</form>

This pattern (and redirects) is supported by common services; see their docs for exact parameter names and absolute-URL requirements. (formsubmit.io)

If you prefer to keep processing on the client, intercept the submit event, POST with fetch (if the endpoint allows CORS), then redirect the browser to a local thank-you page while appending encoded values (URLSearchParams) so the page can show what was sent. Example pattern:

<script>
document.querySelector('form').addEventListener('submit', async function(e){
e.preventDefault();
const fd = new FormData(e.target);
const params = new URLSearchParams(fd);
try {
await fetch(e.target.action, { method:'POST', body: fd, mode:'cors' });
location.href = '/thank-you.html?' + params.toString();
} catch (err) {
e.target.submit(); // fallback
}
});
</script>

Note: fetch to a different origin can be blocked by CORS unless the form service allows it — plan for that fallback. (developer.mozilla.org)

A very low-tech trick: post the form to a hidden iframe (set target="hidden_iframe" and include a hidden <iframe name="hidden_iframe">) so the visible page never navigates; detect the iframe’s load event and then navigate the parent to your thank-you page. You cannot read iframe content if it’s cross-origin, but you can detect completion and redirect. Use postMessage for cross-origin communication if the processor supports it. (developer.mozilla.org)

Recommendation: if you want minimal fuss and reliable redirect+storage, pick a form service (configure its redirect) — it’s the simplest fix when your host forbids custom server scripts.

Recommended Answers

All 3 Replies

I don't believe this is possible unless you are using a custom form script. Is the script (cgi, php, etc) that you are using for the form provided to you by Geocities? Does Geocities allow you to run your own custom scripts?

Geocities won't let me put my own scripts on there for "security reasons". I searched for cgi and pearl on the geocities help, but my internet is acting up so i didn't find much out.

I don't know much about cgi or peal, but i was using a cgi script that geocities gave me to put in my form tag.

If you cannot modify the script, you may consider using meta refresh tag. Thus the page will show as it is and after some time, e.g. 3 seconds, the user will be redirected to a different page. Of course you must explain the user what is happening.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.