Home/ Questions/Q 6547979
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T11:53:44+00:00

I’ve got a questionnaire with some fields checking (written on PHP + HTML). So

  • 0

I’ve got a questionnaire with some fields checking (written on PHP + HTML). So i send data over https.

It works like this

<form id="frm_order" method="post" action="https://site/service_for_businesses" autocomplete="off">
<input name="username" id="username" size="40" maxlength="500" type="text" value="">
<button name="Submit" id="Submit" value="Отправить" type="submit" onclick="return final_check();"></button>
</form>

After a user clicks Submit Button all the data is moved to $_SESSION[‘params’] and then is passed to HELPER class where this data is being checked. If everything is ok then a user is redirected to “SUCCESS PAGE” (this part works fine), but if there is any mistakes in USER’s data from the form fields then $_SESSION[..] is passed to VIEW-controller and the page is refreshed and warnings appear near form fields where there is a mistake.
The problem is that there is a strange behaviour like this:

1) i wrote some data, for example i wrote down a username “Mi%^XS”
2) pressed Submit
3) there is an error in checking data, cause users are not allowed to use special symbols so there is a redirect
4) i saw a page with my wrong username and a warning below
5) i did nothing but just pressed SUBMIT -> redirect
6) i got empty fields with no warnings
7) i pressed SUBMIT -> redirect
8) i got the same thing as in the step 4 -my username with warnings
etc

i cannot understand why.

My website is deployed to 2 web-servers (to avoid DdoS) with balancer.
It’s like there are 2 session with the same ID on both of the servers

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    by default, php generates session ids and stores them in the directory defined by session.save_path in the php.ini

    Also, if you send to php a session cookie that does not exist, php will create the corresponding session.

    So, if you make a request on server 1 that creates a session, it will create a cookie for that session. If you then switch to server 2, it will recognize the session cookie, and if the session already exists, it will use it (your case obviously). In that case, you have the same session ID for 2 servers with distinct data on each.

    The solution to that problem is to store the sessions in a place that is common for the 2 servers (e.g a database). See : http://fr.php.net/manual/en/function.session-set-save-handler.php

    • 0