Reputation
287
Top tag
Next privilege 300 Rep.
Create new tags
Badges
3 11
Impact
~17k people reached

  • 0 posts edited
  • 0 helpful flags
  • 69 votes cast
May
22
accepted Using tc to delay packets to only a single IP address
May
22
answered Using tc to delay packets to only a single IP address
May
15
asked Using tc to delay packets to only a single IP address
Jan
2
comment Forwarding requests in Apache if necessary based on subdomain
Thanks. The trouble with an HTTP redirect is that the redirect needs to be transparent. That is, a request for http://customer1.mycompany.com/rails_app/item1 shouldn't simply redirect to http://1.2.3.4/rails_app/item1 or http://customer1.mycompanyineurope.com/rails_app/item1. The URL needs to be the same no matter what server I hit. That's why I was thinking a reverse proxy in Apache would be the only way to do this.
Jan
2
revised Forwarding requests in Apache if necessary based on subdomain
added 506 characters in body
Jan
2
comment Forwarding requests in Apache if necessary based on subdomain
Christopher, @Khaled: That's true, and a possible alternative to our current idea of using GeoIP DNS. However, even in that case, there could still be requests that end up at the wrong server when an account is first created, or when it is moved from one server to another. For various reasons, we don't want to set a really low TTL. (updating question with this info)
Jan
2
asked Forwarding requests in Apache if necessary based on subdomain
Jan
2
answered Run a job once at a specific time
Dec
30
answered Error pushing to remote with git
Dec
16
awarded  Supporter
Dec
11
awarded  Teacher
Dec
11
answered URL-based request rate limiting in Apache
Dec
11
awarded  Scholar
Dec
11
accepted URL-based request rate limiting in Apache
Dec
9
awarded  Editor
Dec
9
revised URL-based request rate limiting in Apache
added 142 characters in body
Dec
9
comment URL-based request rate limiting in Apache
Thanks for the suggestions, @Ladadadada. I had found the bandwidth limiting modules, but I really need request limiting. Also, I am hosting a number of services (Subversion, Rails app, etc), and rate limiting needs to happen across them, so I would need the limiting to be both high-performance and application agnostic. Otherwise your throttle.php idea would work. Ill update my question. I'm thinking that "You can't do this" might be the correct answer, but let's see if anyone else has any suggestions.
Dec
8
awarded  Student
Dec
8
asked URL-based request rate limiting in Apache