Does nginx proxy handle well on SEESSION ID? [closed] - apache

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
For example,
I have a nginx server as a front-end and two apache servers with mod_php.
As you know, php has sesssion support, which set a cookie identifying the SESSION ID but the real data is stored at the server.
When a user is set with this kind of cookie by one apache server, will his other HTTP requests be fowarded to the same apache server before the session/cookie expires ?

Out of the box, no, the requests will not necessarily be forwarded to the same server, so your application using sessions will be broken.
Go to your favorite search engine and type "nginx affinity" and "nginx sticky" for solutions.

Yes, it will do that if you follow the documentation for multiple back-end servers usage:
http://wiki.nginx.org/HttpUpstreamModule
But better consider storing sessions in a some sort of shared storage, e.g. Memcached or a database.

Related

Moving site; new SSL [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I have a site on AWS with an SSL. The site is an ec2 instance and runs WordPress.
I wanted to move the site out of Wordpress, so I have a different ec2 instance with the new site.
The domain will remain the same and I want to minimize downtime during the switchover. Can I get a new SSL for the new site before the domain DNS points there? I know the connection won't show it's secure until the SSL it matches the domain.
Is there another way to handle the migration?
If the domain isn't changing then as far as SSL is concerned neither is your site. You just need to properly configure the new site to use the same SSL certificate. To minimize downtime move the AWS Elastic IP to the new ec2 instance during migration. If done correctly you'll have no downtime at all.

Is intercepting TCP/IP traffic easy if i use RC4 SSL Cipher suites? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am having a server which supports RC4 SSL Cipher suites. I just want to know whether it is easy for a attacker to determine the contents and IP of the users who are connecting to my server?
Concerning the IP, that is out of scope for SSL. SSL works on top of TCP and thus doesn't even know about IPs. Hiding IPs is hard, since they're required to deliver data to the correct recipient. You can use proxies like TOR to hide your IP.
SSL keeps the content transferred over the encrypted connection secret. RC4 isn't the greatest encryption since it produces a biased bitstream. That allows an attacker to learn your secret data if it's transferred several billion times at a known position close the the beginning of the stream.

Why does it cost $20 a month for Custom-domain SSL on Heroku? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Please note this is not a complaint. I am just wondering what the cost is to Heroku for providing custom-domain SSL, if there is one, as they do not provide the SSL certificate. As i understand it it is quite common to provide SSL support for free, and charge for the certificate itself.
For reference: Custom-domain SSL
In order to use your own SSL certificate with a shared server, your site must run on its own dedicated public IP address.
(since the server needs to send the SSL cert before the browser tells it which host it's connecting for)
IP addresses are a scarce commodity.

Block CNAME redirect from a domain I don't own [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Someone has registered a domain and is using a CNAME redirect to direct traffic to my site. Google is seeing this as duplicate content and it's affecting my rankings.
Is there anyway of blocking access for traffic that comes to my site through the domainnotundermycontrol.com redirect?
Thanks in advance.
"There is no BAD publicity."
The CNAME is solely a DNS tool. The request to you server should still be sending a request for the domainnotundermycontrol.com/somepage to your apache server once it gets you're IP from the DNS lookup. Apache will see the 'ServerName' as domainnotundermycontrol.com
It sounds like the domain which you CAN control has no filtering on server name, only ip, maybe. Create a vhost for the domainnotundermycontrol.com on your server to catch all requests to that server name and serve up an index file with links to legitimate page you want people to hit or just some adwords. Then it will no longer be caught by your other vhost.
Enjoy the free traffic.

Rewriting Amazon S3 static urls [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
In the interest of hosting purely static sites from Amazon S3, is the only route to rewrite the URLs and endpoints for accessing it's resources in a friendlier way via a rewrite engine such as any web server? And would it best to host this as an EC2?
It seems overkill but wasn't sure if there were alternatives.
I'm not sure why you need to rewrite.
You can assign a DNS CNAME to an S3 bucket for DNS. And they recently started supporting a default document.
So you can perfectly host http://www.example.com/ or http://www.example.com/some/path/to/some/file.html
http://aws.typepad.com/aws/2011/02/host-your-static-website-on-amazon-s3.html
S3 offers no features to 'rewrite' URLs as keys are immutable.
If you want to use URLs that are different from the S3 key you'll have to proxy the requests yourself.