https://bz.apache.org/bugzilla/show_bug.cgi?id=59319
--- Comment #2 from Ben RUBSON <[email protected]> --- Rainer, First of all, thank you very much for your long, detailed, precise answer... I really appreciate it ! So undestood, "https://${proxytouse}"; will never be targeted by a resolved worker, "https://host1:port1"; in your example. Let's asume it would, some parameters such as connection pooling in a worker like "https://${proxytouse}"; would not really makes sense, as in reality it would address many different addresses/ports. To work, a new worker (a clone of the default worker with specific user defined parameters applied) would have to be created internally each time the generic one is resolved to a new value. Unfortunately as you said there is no possibility to enforce default values for the default worker. Once again some values would certainly not make sense for the default worker (connection pooling...), but some of them, such as for example connectiontimeout, timeout... would be worth it. In my use case, I have many host/port pairs which vary upon the system's configuration and furthermore change over time. So a uniq configuration with variables is very practical. I could think about the following : each time a new host/port pair arrives on the server, automatically create its small configuration file containing only the following macro line : Use MyWorker hostX:portX And reload the Apache configuration. Macro would be defined in the main configuration. The main configuration would also contain something like : Include /path/to/workers/configurations/worker.*.conf Of course being able to define default parameters for the default worker (or for its clones) would be even easier / cleaner. That's another story but, declaring a worker for each host:port would activate connection pooling for each one of them. I think connection pooling would be work it in my use case : each time a user connects to the service, it is forwarded to the same reserve proxy. So connection pooling could be a good thing to have. However, can connection pooling have an impact in terms of performance if Apache has to manage many workers ? Can we tend to somethig like denial of service if the maximum number of connection in pools is reached, and no other connections to other workers can be made ? Or is there no limit at all here ? Being able to define default worker (or clones of worker) parameters would also improve P flag of mod_rewrite. Thank you again, Best regards, Ben -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
