So i finally got apache2-devel installed... However, when running
./configure for mod_proxy_msrpc, i get an error due to the absence of
ap_socache.h. It appears this file is included n apache 2.4. Now, will
mod_proxy_msrpc only work in apache 2.4? If not, can i just get the
ap_socache.h file
Chris, if you encounter any issues with mod_proxy_msrpc please report them
at https://github.com/bombadil/mod_proxy_msrpc/issues. Note that OAB, OWA,
Autodiscover, ActiveSync, etc. all use normal HTTP/S (and not MSRPC like
OA) so they should work without mod_proxy_msrpc. There is an open issue
If you use httpd as reverse proxy then clients will perform SSL handshakes
with your reverse proxy. In SSL there is no distinction between decrypting
the HTTP headers only or decrypting the full HTTP request - it's simply
payload and it will be decrypted as a whole. If you want to understand
how
http://domain_name* redirects
to *http://domain_name:3030 http://domain_name:3030*
Also tries Redirect
*Redirect :3030 http://domain_name http://domain_name*
rewrite_module is enabled.
Is there any config error or the approach is bad.
On Monday 10 February 2014 06:21 PM, Thomas Eckert
*VirtualHost *:3030* ... */VirtualHost*
On Thu, Feb 13, 2014 at 3:16 PM, Thomas Eckert
thomas.r.w.eck...@gmail.com wrote:
I'm confused as to what your setup and intention is. From your original
message I assumed you were talking about a normal server but your
configuration example looks like
Assuming you have a working config for a server/vhost on domain_name:3030,
then how about
Redirect permanent / http://domain_name:3000/
? See http://httpd.apache.org/docs/current/mod/mod_alias.html#redirect and
friends.
Restricted access is a bit vague but
The question is: from the proxy performance/scalability point of view is
it better to configure backends (origin servers) with http or with https?
Better depends on what you want to achieve. Do you want to securely
deliver simple html content with no fancy stuff ? Do you want to have
Can you post the headers, from sending the request(s) up to and including
the response(s) ?
I think you might be hitting the same spot as I recently did in (1). In
short, most (if not all) popular clients do not unpack responses if they
think they shouldn't even if the headers tell them to. So
Using form based auth, e.g.
Location /foo
AuthName forms_foo
AuthFormProvider my_provider
AuthType form
AuthFormLoginRequiredLocation /foo_form
Session On
SessionCookieName foo_cookie path=/foo/;httponly
SessionCryptoPassphrase somereallyneatandnicepassphrase
Did you make sure to have the -dev package(s) installed ?
On Mon, Dec 16, 2013 at 10:10 AM, Abdul Anshad ab...@visolve.com wrote:
I have made sure that the --with-ssl points to the 1.0.1e, FYI i also
have another system binary installed which is openssl-0.9.7d.
I have included the source
to install 2.4.x dev ?
Regards,
Abdul
On 12/16/2013 2:48 PM, Thomas Eckert wrote:
Did you make sure to have the -dev package(s) installed ?
On Mon, Dec 16, 2013 at 10:10 AM, Abdul Anshad ab...@visolve.com wrote:
I have made sure that the --with-ssl points to the 1.0.1e, FYI i also
have
I've tried something simliar but didn't get it working. I would be
interested in how your attempts on automatic-form-filling-in worked out -
and if they did also in the how ;-)
On Thu, Nov 28, 2013 at 11:48 AM, iridium1191 iridium1...@gmail.com wrote:
Hi Apache users,
I'm running Apache
Using mod_auth_form, when a user tries to access a URL and is 'interrupted'
by the form based login, how do I pass on the original URL to the form html
or to the AuthFormLoginSuccessLocation directive, so I can redirect the
client - upon successful login - to the URL where she wanted to go to.
At
Trying to figure out how to unset encrypted cookies for which the
encryption key was changed. Docs at
http://httpd.apache.org/docs/current/mod/mod_session_crypto.html
say
If the encryption key is changed, sessions will be invalidated
automatically.
but using a config like
Location /
Try setting the proxy-initial-not-pooled flag with mod_proxy_http, see
http://httpd.apache.org/docs/current/mod/mod_proxy_http.html
Apache 2.4 has an issue with the HTTP keep-alive time out which happens
quite frequently with ActiveSync. There is an ongoing discussion
(mod_proxy, oooled backend
Using a config like this
Proxy balancer://cd107d9706d71153bafd4ab15f1c6b5d
BalancerMember http://backend.example.local status=-SE
/Proxy
VirtualHost 10.10.10.10:80
ServerName frontend.example.local
SSLProxyEngine On
RequestHeader set X-Forwarded-Proto http
I'm looking for the erorr in this config :
KeepAlive OnServerName server1.domain1.localServerAdmin
me@domain1.localListen 10.10.10.10:80 httpProxy
balancer://cd107d9706d71153bafd4ab15f1c6b5d
BalancerMember http://server1.domain2.local
status=-SE/ProxyVirtualHost 10.10.10.10:80
This is interesting. I'm seeing similar events at one of my reverse proxy.
After fixing a DNS infrastructure problem I started seeing lots of 304s
with processing times well above 5 seconds. For header-only requests that's
a lot of time. If there is any news here please let us know. At the very
In a simple reverse proxy setup, such as
Proxy balancer://cd107d9706d71153bafd4ab15f1c6b5d
BalancerMember http://mydomain.org
status=-SE/ProxyVirtualHost 10.10.10.10:80
ServerName secure.mydomain.local
SSLProxyEngine On
RequestHeader set X-Forwarded-Proto http
On 11/16/2012 05:12 PM, Nick Kew wrote:
On Fri, 16 Nov 2012 11:31:38 +0100
Thomas Eckertthomas.eck...@sophos.com wrote:
Thanks for the hint but unfortunately manually adding xml2enc to the
filtering chain does not help.
Looks like you've got problems over and above anything to do with
your
Is the directive
SSLStrictSNIVHostCheck On
meant to block connections to a virtual host if the connecting client
uses an IP literal as URL ? RFC 6066 states that
Literal IPv4 and IPv6 addresses are not permitted in HostName.
since a SNI doesn't make sense at all for an IP literal and
On 11/14/2012 06:12 PM, Nick Kew wrote:
On 14 Nov 2012, at 15:53, Thomas Eckert wrote:
Is there a way to work around this ? I do want the call to mod_xml2enc to
happen but I also want the reverse proxy to support content compression.
That's a lot of correct analysis.
The output chain you
Hi folks
I'm using apache (2.4.3) as reverse proxy with mod_proxy_html (as
delivered with 2.4.3) and encountered an issue using HTML rewriting in
combination with content compression, as with the Accept-Encoding and
Content-Encoding HTTP headers.
This issue has been encountered by numerous
23 matches
Mail list logo
