cbaltatescu's questions

I need to take a look at all the headers of certain requests. I've been reading the haproxy manual, I am able to use capture to log whatever header I KNOW is there.

But I would like to see ALL the headers, unknown to me, that the app receives. Is this possible with haproxy's logging options? Some sort of regexp or iteration method?

I am using haproxy 1.6

Thank you.

Possible Duplicate:
How to have a certificate which works with both example.com and subdomain.example.com in IIS?

I've been looking for a solution to the following problem for a few days now. I have domain.com for which I have bought and installed a wildcard certificate so now I can provide secure access to www.domain.com or whatever.domain.com. This works. However, even though the application thar runs on these subdomains makes sure no one gets to visit an URL that doesn't contain at least www as the subdomain, you can still delete the www part. Once you do that no serverside redirects will help if you are on https because the browser will not fulfil the request because the wildcard ssl certificate will not cover the naked domain (domain.com)

So my question is this:

1. Can I get a wildcard ssl from a provider that will also cover the naked domain? Is that even possible?
2. If no for 1 above, if I purchase a basic SSL cert for domain.com will I be able to install it (Apache) on the same server and same IP as the wildcard one is installed on?
3. If answer is No for both and 1 and 2 what are my options? I find it really annoying that securing a domain AND it's subdomains is that complicated :)

[EDIT]: Forgot to mention that of course I would prefer and option with no costs involved, but if that's not possible, then I guess I would prefer number 2 because the costs for a basic SSL cert are lower then for a new Wildcard one.

Thank you.

After digging around to understand how to setup replication using gluster I've come across this question: Can Apache Read The GlusterFS Brick Directly But Write To The GlusterFS Mount?

I've also found a how that seems to explain the same thing, and I thought I understand it, but now I think I don't.

So in order to get this kinf of replication I need to have both machines function as servers and clients at once? Now I don't understand how the relationship works: isn't B, for example a client of A?

Are there more than one level of client-server relationships involved? Is A a client for A and B a client for B, each mounting in a folder a volume from the same machine and those 2 volumes somehow are in sync (from A to B) in a 3rd layer of relationships?

Why is the question above asking about writing to the file-system or to the mounted volume? When I make B a client to A, with A exporting a folder and B mounting it as a remote volume in a folder I never asked my self what I was writing on: i wrote into the original folder on A and into the mounted volume on B. Isn't this how it's supposed to work?

I've been playing with gluster for the last 2 days and been asking questions here and on their questions system. I really don't understand some of the stuff. I see people saying stuff like

Set up replicated bricks between the servers (since you are only using 3, replicated would be safer), and each server will see the files of all other servers as being 'local' - even if one server fails, the files have been replicated to the other servers.

or

Gluster will maintain the file synchronization across volumes (bricks), and has 'self-healing' capabilities that will deal with any inconsistencies due to one server being offline.

Since I mount a remote volume from the server to the client(s) how does gluster handle failure of the server node, the one the volumes are mounted from? From what I've tried the folder on the client where the volume was mounted becomes inaccessible and I have to use umount to unblock it. And after that there no content from the server.

This is, basically what I don't see covered in any explanations: what happens when the server node fails and whether it's possible to really replicate the content, like unison or rsync does?

I need to implement some sort of HA setup where 2 servers need to be able to always be in sync, no matter on which one you write on. The DB part can be covered by a master-master replication setup. However, when it comes to files and content I haven't been able to find something to suit these needs very well. I need to be able to replicate /var/www for example from one machine to the other and be able to write in any of them and always have the same content available no matter where the http request goes to.

• unison: easy to use, simple concept, however it's more like a 2-way rsync, there is no automatic propagation of file changes, unless you run it with its repeat option. I'm not sure how reliable that is. I was hoping for a daemon-like feature that would 'watch' changes to a folder's content.
• glusterfs: easy to configure, a nice project, seems to be perfect for what I need, however, it doesn't seem to handle this 2-way.
• xtreemfs: difficult to configure if you want replication (the docs are a bit hard to follow) and seems to be intended for the "distributed filesystem" part more than for the replication aspect.
• ceph: similar to gluster, but again, don't think it handles 2-way replication.
• mogilefs: not transparent, the application that you build needs to be aware of it and use it's services to access the file system. Not something I can use.

So I'm not sure if either 2-way replication is something that is usually not done and I need to reconsider this or I haven't researched this enough, but I'm at a loss. I don't seem to find other solutions.

Is there anything else out-there that can handle automatic transparent 2-way file replication?