Otdfbt

Plagiarism or not?

CAST throwing error when run in stored procedure but not when run as raw query

If human space travel is limited by the G force vulnerability, is there a way to counter G forces?

Could the museum Saturn V's be refitted for one more flight?

How to prevent "they're falling in love" trope

How much of data wrangling is a data scientist's job?

Zip/Tar file compressed to larger size?

Why do bosons tend to occupy the same state?

In 'Revenger,' what does 'cove' come from?

How badly should I try to prevent a user from XSSing themselves?

What does “the session was packed” mean in this context?

Size of subfigure fitting its content (tikzpicture)

Are there any examples of a variable being normally distributed that is *not* due to the Central Limit Theorem?

Do UK voters know if their MP will be the Speaker of the House?

Is it inappropriate for a student to attend their mentor's dissertation defense?

Unlock My Phone! February 2018

How to show a landlord what we have in savings?

What method can I use to design a dungeon difficult enough that the PCs can't make it through without killing them?

How to tell a function to use the default argument values?

One verb to replace 'be a member of' a club

How to Recreate this in LaTeX? (Unsure What the Notation is Called)

How seriously should I take size and weight limits of hand luggage?

How does a predictive coding aid in lossless compression?

What reasons are there for a Capitalist to oppose a 100% inheritance tax?

Maintaining single TLS handshake state across multiple subdomains on the same server

SSL on multiple subdomains with the same IPTwo Nginx subdomains with different root folders but both going to the same?Multiple domains and subdomains with SSL on single server with NGINXTwo https virtualhosts on same server: same port, different subdomainsRedirect from port 80 to 443 with nginx and multiple serversHow to redirect all HTTP requests to HTTPS AND redirect all nonexistent subdomains to one specific domainMultiple Domains and Subdomains on one IP Apache2Root domain and subdomains on the same SAN certificate?How to manage multiple sites on the same server with Nginx?Communicate SSL handshake failure info between two NGINX servers

0

I currently have two different subdomains that I would like to host on a single server. The scenario that I wish to implement is when the first domain fails due to an SSL handshake error, the second domain should be able to redirect to a new third subdomain based on this failure information (for the same client). Therefore, while the first subdomain is unable to complete the TLS handshake and move on to the HTTP layer to do the redirect, the second domain is still alive and waiting to see whether the TLS handshake for the first domain got rejected or not.

From my current beginner knowledge of how servers are implemented, I believe that communicating this TLS state across two servers may not be possible. However, I am wondering whether this is something that is doable if I have a single server handling all the subdomains. Can I for example, maintain a single store of information about the TLS states connected with the two subdomains? Is this something that may be possible in either NGINX or APACHE server configurations? Or via some other route?

One of the possibilities I have explored is the map command inside nginx where you can set up a variable, and then read it inside the server. Could something like this be also used? For example, I could set up the variable inside subdomain one if the handshake has failed, and then read the variable when I am about to redirect from the second subdomain to do a conditional redirect.

Alternatively, since my ultimate requirement is to be able to redirect from subdomain-one to subdomain-three if subdomain one fails, can I just redirect to a new subdomain using the error directive if I notice 492 error code (which specifies whether there is an error in the client verfication process) as mentioned over here. I have tested this by adding an error page:

error_page 492 /home/vagrant/flask_app/app_name/app/static/images/pixel_fail.png

but it doesn't seem to be working.

Would very much appreciate help regarding this.

nginx ssl apache2

share|improve this question

edited yesterday

QPTR

asked 2 days ago

QPTRQPTR

992

New contributor

QPTR is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  So, basically subdomain one and two are both loaded at the same time. Subdomain one fails on handshake, and subdomain two is holding off its response until it somehow knows that the first subdomain has failed. So, while I cannot redirect via subdomain one (which you rightly pointed out cannot redirect until the TLS handshake has been completed), I can still redirect using subdomain two. So, my question is whether a sharing of state (via some sort of variable or anything else) is possible between the two subdomains since they are both on the same server.
  
  – QPTR
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Rather than add comments please delete the comment and edit your post to make sure it contains all the information someone would need to help solve your problem. Make it easy for people to help you. Suggest you remove the "edit" section of your post and make it a single, consistent, easy to understand question.
  
  – Tim
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Tim This comment was a response to a question asked in the comments, which I believe they deleted later. But yes, I will make it more consistent.
  
  – QPTR
  yesterday
  

  
  
  
  

add a comment | 

0

I currently have two different subdomains that I would like to host on a single server. The scenario that I wish to implement is when the first domain fails due to an SSL handshake error, the second domain should be able to redirect to a new third subdomain based on this failure information (for the same client). Therefore, while the first subdomain is unable to complete the TLS handshake and move on to the HTTP layer to do the redirect, the second domain is still alive and waiting to see whether the TLS handshake for the first domain got rejected or not.

From my current beginner knowledge of how servers are implemented, I believe that communicating this TLS state across two servers may not be possible. However, I am wondering whether this is something that is doable if I have a single server handling all the subdomains. Can I for example, maintain a single store of information about the TLS states connected with the two subdomains? Is this something that may be possible in either NGINX or APACHE server configurations? Or via some other route?

One of the possibilities I have explored is the map command inside nginx where you can set up a variable, and then read it inside the server. Could something like this be also used? For example, I could set up the variable inside subdomain one if the handshake has failed, and then read the variable when I am about to redirect from the second subdomain to do a conditional redirect.

Alternatively, since my ultimate requirement is to be able to redirect from subdomain-one to subdomain-three if subdomain one fails, can I just redirect to a new subdomain using the error directive if I notice 492 error code (which specifies whether there is an error in the client verfication process) as mentioned over here. I have tested this by adding an error page:

error_page 492 /home/vagrant/flask_app/app_name/app/static/images/pixel_fail.png

but it doesn't seem to be working.

Would very much appreciate help regarding this.

nginx ssl apache2

share|improve this question

edited yesterday

QPTR

asked 2 days ago

QPTRQPTR

992

New contributor

QPTR is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  So, basically subdomain one and two are both loaded at the same time. Subdomain one fails on handshake, and subdomain two is holding off its response until it somehow knows that the first subdomain has failed. So, while I cannot redirect via subdomain one (which you rightly pointed out cannot redirect until the TLS handshake has been completed), I can still redirect using subdomain two. So, my question is whether a sharing of state (via some sort of variable or anything else) is possible between the two subdomains since they are both on the same server.
  
  – QPTR
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Rather than add comments please delete the comment and edit your post to make sure it contains all the information someone would need to help solve your problem. Make it easy for people to help you. Suggest you remove the "edit" section of your post and make it a single, consistent, easy to understand question.
  
  – Tim
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Tim This comment was a response to a question asked in the comments, which I believe they deleted later. But yes, I will make it more consistent.
  
  – QPTR
  yesterday
  

  
  
  
  

add a comment | 

I currently have two different subdomains that I would like to host on a single server. The scenario that I wish to implement is when the first domain fails due to an SSL handshake error, the second domain should be able to redirect to a new third subdomain based on this failure information (for the same client). Therefore, while the first subdomain is unable to complete the TLS handshake and move on to the HTTP layer to do the redirect, the second domain is still alive and waiting to see whether the TLS handshake for the first domain got rejected or not.

From my current beginner knowledge of how servers are implemented, I believe that communicating this TLS state across two servers may not be possible. However, I am wondering whether this is something that is doable if I have a single server handling all the subdomains. Can I for example, maintain a single store of information about the TLS states connected with the two subdomains? Is this something that may be possible in either NGINX or APACHE server configurations? Or via some other route?

One of the possibilities I have explored is the map command inside nginx where you can set up a variable, and then read it inside the server. Could something like this be also used? For example, I could set up the variable inside subdomain one if the handshake has failed, and then read the variable when I am about to redirect from the second subdomain to do a conditional redirect.

Alternatively, since my ultimate requirement is to be able to redirect from subdomain-one to subdomain-three if subdomain one fails, can I just redirect to a new subdomain using the error directive if I notice 492 error code (which specifies whether there is an error in the client verfication process) as mentioned over here. I have tested this by adding an error page:

error_page 492 /home/vagrant/flask_app/app_name/app/static/images/pixel_fail.png

but it doesn't seem to be working.

Would very much appreciate help regarding this.

nginx ssl apache2

share|improve this question

edited yesterday

QPTR

asked 2 days ago

QPTRQPTR

992

New contributor

QPTR is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited yesterday

QPTR

asked 2 days ago

QPTRQPTR

992

New contributor

QPTR is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited yesterday

QPTR

asked 2 days ago

QPTRQPTR

992

New contributor

QPTR is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 2 days ago

QPTRQPTR

992

New contributor

QPTR is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 2 days ago

QPTRQPTR

992