Re: [users@httpd] mod_md questions
On Mon, 28 Feb 2022, Gillis J. de Nijs wrote: It does mention it, but I agree it's not too straightforward. https://httpd.apache.org/docs/current/mod/mod_md.html says (emphasis mine): "If Let's Encrypt can verify the ownership of the domain, the module will retrieve the certificate and its chain, store it in the local file system (see MDStoreDir) and provide it, on next restart, to mod_ssl." Yes, there's an entire "How to manage server reloads" section over in the readme of https://github.com/icing/mod_md, and somehow that info never made it in to the official docs. -- "SOY BOMB!" -The Chest of the nameless streaker of the 1998 Grammy Awards' Bob Dylan Performance. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC FB: fb.com/DanielMahoneyIV LI: linkedin.com/in/gushi Site: http://www.gushi.org --- - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] ProxyPass option mapping=servlet hurts mod_rewrite
Hi Yann, > RewriteRule "^/alpha/gobeta/(.*)$" http://server2.localnet:8080/beta/$1 [P] If the RewriteRule is specified with the option [P] it works correctly. The request https://example.ort/alpha/gobeta/anypath is sent to the beta backend. > Also, it seems to me that "/alpha/gobeta/.." is not matched by the > "ProxyPass /beta ...", so it really boils down to the RewriteRule only. > What do you expect here? But when I take the option [PT] the behavior changes. Without "mapping=servlet" the request is sent to the beta backend. With "mapping=servlet" the request is replied by a 404 NOT FOUND. - Is this change of behavior acceptable? Maybe it is acceptable cause the option [PT] is the wrong choice if I want the request to be replied by the proxied beta backend. But some inexperienced admins will run into trouble. (like me ;-) Regards, Hendrik
RE: [users@httpd] migrate apache httpd from 2.4.17 to 2.4.48
Hello katz, Thanks for your reponse, but I don’t find the 2.4.48 version that I search on ApacheLounge, can you maybe gave another linke please to download it About how it installed, how can I know please if it installed or juste a package and service Cordialement, Othmane BENMOUSSA Ext / HELPLINE Equipe Production IT Technical Team Direction Digitale +33 (0)4 72 18 68 52 [signature_1448240921] De : Yehuda Katz Envoyé : jeudi 3 mars 2022 12:31 À : users@httpd.apache.org Objet : Re: [users@httpd] migrate apache httpd from 2.4.17 to 2.4.48 It depends how you installed it originally. There is no official Windows package of HTTPD, but there are a number of other people/groups who make such builds available. I personally use the package built by ApacheLounge. It has no installer - I install it by unzipping to C:\Webserv\Apache and running `httpd -k install` and `httpd -k start` on an elevated Command Prompt. To upgrade, I stop the server, rename the old installation folder as a backup, unzip the new folder, copy the old config over the new, and start the server again. I rarely need to change my configuration, but I usually copy the whole config folder using a program called Beyond Compare, a graphical diff tool, so I can see if any of the default settings changed. If you have a different distribution, you may have an installer or you may have other components that need to be upgraded at the same time, so if you need more help, we need more information about your current system. - Y Sent from a device with a very small keyboard and hyperactive autocorrect. On Thu, Mar 3, 2022, 5:39 AM BENMOUSSA Othmane mailto:ext-benmou...@em-lyon.com>> wrote: Hello, I need to migrate apache from version 2.4.17 to 2.4.48 on a 64bits windows server, I can't find the migration guide on the apache website, can you please send me a migration procedure. version 2.4.48 is the latest version supported by my application Thanks to share you experiences with mer Cordialement, Othmane BENMOUSSA Ext / HELPLINE Equipe Production IT Technical Team Direction Digitale +33 (0)4 72 18 68 52 [signature_1448240921] Ce message électronique et tous les fichiers attachés qu'il contient sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le retourner à son émetteur. Les idées et opinions présentées dans ce message sont celles de son auteur, et ne représentent pas nécessairement celles de l’institution ou les entités affiliées dont dépend l’auteur. La publication, l'usage, la distribution, l'impression ou la copie non autorisée de ce message et des attachements qu'il contient sont strictement interdits ». “This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please return it to the sender. The ideas and views expressed in this email are solely those of its author, and do not necessarily represent the views of the institution or company the author is dependent from. Unauthorized publication, use, distribution, printing or copying of this e-mail or any attached files is strictly forbidden. Ce message électronique et tous les fichiers attachés qu'il contient sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le retourner à son émetteur. Les idées et opinions présentées dans ce message sont celles de son auteur, et ne représentent pas nécessairement celles de l’institution ou les entités affiliées dont dépend l’auteur. La publication, l'usage, la distribution, l'impression ou la copie non autorisée de ce message et des attachements qu'il contient sont strictement interdits ». “This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please return it to the sender. The ideas and views expressed in this email are solely those of its author, and do not necessarily represent the views of the institution or company the author is dependent from. Unauthorized publication, use, distribution, printing or copying of this e-mail or any attached files is strictly forbidden.
Re: [users@httpd] migrate apache httpd from 2.4.17 to 2.4.48
It depends how you installed it originally. There is no official Windows package of HTTPD, but there are a number of other people/groups who make such builds available. I personally use the package built by ApacheLounge. It has no installer - I install it by unzipping to C:\Webserv\Apache and running `httpd -k install` and `httpd -k start` on an elevated Command Prompt. To upgrade, I stop the server, rename the old installation folder as a backup, unzip the new folder, copy the old config over the new, and start the server again. I rarely need to change my configuration, but I usually copy the whole config folder using a program called Beyond Compare, a graphical diff tool, so I can see if any of the default settings changed. If you have a different distribution, you may have an installer or you may have other components that need to be upgraded at the same time, so if you need more help, we need more information about your current system. - Y Sent from a device with a very small keyboard and hyperactive autocorrect. On Thu, Mar 3, 2022, 5:39 AM BENMOUSSA Othmane wrote: > Hello, > > I need to migrate apache from version 2.4.17 to 2.4.48 on a 64bits windows > server, I can't find the migration guide on the apache website, can you > please send me a migration procedure. > > version 2.4.48 is the latest version supported by my application > > > > Thanks to share you experiences with mer > > > > Cordialement, > > > > *Othmane BENMOUSSA* > > *Ext / HELPLINE* > > Equipe Production > > *IT Technical Team* > > Direction Digitale > > > > +33 (0)4 72 18 68 52 > > > > [image: signature_1448240921] > > > Ce message électronique et tous les fichiers attachés qu'il contient sont > confidentiels et destinés exclusivement à l'usage de la personne à laquelle > ils sont adressés. Si vous avez reçu ce message par erreur, merci de le > retourner à son émetteur. Les idées et opinions présentées dans ce message > sont celles de son auteur, et ne représentent pas nécessairement celles de > l’institution ou les entités affiliées dont dépend l’auteur. La > publication, l'usage, la distribution, l'impression ou la copie non > autorisée de ce message et des attachements qu'il contient sont strictement > interdits ». “This email and any files transmitted with it are confidential > and intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please return it to > the sender. The ideas and views expressed in this email are solely those of > its author, and do not necessarily represent the views of the institution > or company the author is dependent from. Unauthorized publication, use, > distribution, printing or copying of this e-mail or any attached files is > strictly forbidden. >
Re: [users@httpd] ProxyPass option mapping=servlet hurts mod_rewrite
On Thu, Mar 3, 2022 at 12:24 PM Yann Ylavic wrote: > > Hi Hendrik; > > > > > after reading your commit comment in https://svn.apache.org/r1898509 I > > realised that one important test case is missing: > > What happens if mod_rewrite manipulates the URL of a target that is proxied > > with the option mapping=servlet? > > > > From my point of view this test case fails. :-( > >ProxyPass /beta http://server2.localnet:8080/beta mapping=servlet > >RewirteRule "^/alpha/gobeta" /beta [PT,L] > > Calling https://example.org/alpha/gobeta/test sends back a 404 instead > > the beta content. > > In this case mod_proxy could not map the requests to the beta backend. > > Given that "ProxyPass ... mapping=servlet" applies before the > RewriteRule, I don't see how you can have a RewriteRule [PT] that > either "cancels" the ProxyPass (like in your RewriteMap examples) > and/or that rewrites the uri but keeps proxying (like in the above > example). > > Isn't: > RewriteRule "^/alpha/gobeta/(.*)$" http://server2.localnet:8080/beta/$1 [P] > (or alike) what you are looking for in the above example? Also, it seems to me that "/alpha/gobeta/.." is not matched by the "ProxyPass /beta ...", so it really boils down to the RewriteRule only. What do you expect here? > > Regards; > Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] ProxyPass option mapping=servlet hurts mod_rewrite
Hi Hendrik; > > after reading your commit comment in https://svn.apache.org/r1898509 I > realised that one important test case is missing: > What happens if mod_rewrite manipulates the URL of a target that is proxied > with the option mapping=servlet? > > From my point of view this test case fails. :-( >ProxyPass /beta http://server2.localnet:8080/beta mapping=servlet >RewirteRule "^/alpha/gobeta" /beta [PT,L] > Calling https://example.org/alpha/gobeta/test sends back a 404 instead the > beta content. > In this case mod_proxy could not map the requests to the beta backend. Given that "ProxyPass ... mapping=servlet" applies before the RewriteRule, I don't see how you can have a RewriteRule [PT] that either "cancels" the ProxyPass (like in your RewriteMap examples) and/or that rewrites the uri but keeps proxying (like in the above example). Isn't: RewriteRule "^/alpha/gobeta/(.*)$" http://server2.localnet:8080/beta/$1 [P] (or alike) what you are looking for in the above example? Regards; Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[users@httpd] migrate apache httpd from 2.4.17 to 2.4.48
Hello, I need to migrate apache from version 2.4.17 to 2.4.48 on a 64bits windows server, I can't find the migration guide on the apache website, can you please send me a migration procedure. version 2.4.48 is the latest version supported by my application Thanks to share you experiences with mer Cordialement, Othmane BENMOUSSA Ext / HELPLINE Equipe Production IT Technical Team Direction Digitale +33 (0)4 72 18 68 52 [signature_1448240921] Ce message ?lectronique et tous les fichiers attach?s qu'il contient sont confidentiels et destin?s exclusivement ? l'usage de la personne ? laquelle ils sont adress?s. Si vous avez re?u ce message par erreur, merci de le retourner ? son ?metteur. Les id?es et opinions pr?sent?es dans ce message sont celles de son auteur, et ne repr?sentent pas n?cessairement celles de l'institution ou les entit?s affili?es dont d?pend l'auteur. La publication, l'usage, la distribution, l'impression ou la copie non autoris?e de ce message et des attachements qu'il contient sont strictement interdits >. "This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please return it to the sender. The ideas and views expressed in this email are solely those of its author, and do not necessarily represent the views of the institution or company the author is dependent from. Unauthorized publication, use, distribution, printing or copying of this e-mail or any attached files is strictly forbidden.
