Tag Info

New answers tagged

0

This should do it: RewriteEngine On RewriteCond %{HTTPS} on RewriteCond %{HTTP_HOST} ^(www\.)?example\.com$ [NC] RewriteRule (.*) http://newexample.com%{REQUEST_URI} [R=301,L]


0

I got the following answer from Juniper Community. This is a known issue in 6.3r19. I would recommend using 6.3r18. By using the following guide i changed the version from, 6.3r19 to 6.3r18: http://kb.juniper.net/InfoCenter/index?page=content&id=KB13672 Note, it is worth removing the Digicert certs before downgrade. They changed in some strange ...


0

For the first problem, try setting your ServerAlias variable to include the following on all virtual host sections. ServerAlias ourdomain.com *.ourdomain.com Ref: http://httpd.apache.org/docs/2.4/mod/core.html#serveralias As per startup error, it appears that a previous run is not shutdown properly i.e. your netstat & lsof output shows that it is ...


0

Yes, this is normal - by default all websites sharing an IP address will be pulled up if going to https://anydomainthatsharesthatip.com. The reason why is that SSL is at a level before HTTP header communication so all Apache has to go on at that stage of the request is the IP address and port being requested (i.e. it hasn't received the HTTP Host: header ...


2

This may be a little more complicated, but if Tumblr doesn't provide an SSL-secured URL you can use, you could set up a proxy site like https://mytumblrproxy.example.com which you run on your server and which proxies all requests to/from your Tumblr blog and then link to that. Be sure you don't violate their terms of service, and also, I'd suggest ...


1

I suggest you to enable AJP connector in both Tomcat and Apache httpd. This binary protocol is dedicated for Java HTTP proxying. Using it may save you configuration time and effort and lower bandwith and resource requirement. Btw., <Proxy *> directive is irrelevant on reverse proxies.


0

Just to follow up on this for others that could not resolve it using the above solution, I had experienced a similar problem whereby the server was delivering the wrong certificate for HTTPS connections to a website with a host header value. In my case, it turned out to be that the binding was set to receive connections from * instead of the actual server ...


1

I believe the reason you're getting too many redirections is because the RedirectMatch will fire even when the URL is requested at https so it keeps redirecting over and over even once it already becomes https. I'd suggest solving this with mod_rewrite. For example: RewriteEngine on RewriteCond %{HTTPS} !=on RewriteRule %{REQUEST_URI} ^(/asia[^/]*/.*)$ ...


0

I had to create a .php so that I request the file through request.php?f=main.jpg instead of requesting it directly like domain.com/main.jpg It's a little ugly work around but it works. Of course I had to add the header Access-Control-Allow-Origin like this. That way I don't need to specify that header in .htaccess file. if (isset($_SERVER['HTTP_ORIGIN']) ...


0

This is how I solved it: Check whether OpenVPN is listening on Port 443 TCP. Check according to the config, as well as an port check service. Set port-share to port-share {IP} {PORT} How to know the {IP} and {PORT}? In nginx: server { listen {IP}:{PORT}; } In Apache: <VirtualHost {IP}:{PORT}> ServerName {IP} ServerAlias {IP} ...


1

Without the complete .htaccess I don't exactly know but when more processing is done within Apache adding the condition always might be needed: Header always set Access-Control-Allow-Origin "*" The manual explains it as follows: When your action is a function of an existing header, you may need to specify a condition of always, depending on which ...


2

IMHO You're already heading the wrong direction with your intention to create a .htaccess file, which is my pet peeve, quoted from from the manual on .htaccess files: You should avoid using .htaccess files completely if you have access to httpd main server config file. Using .htaccess files slows down your Apache http server. Any directive that you can ...


-1

L4.1 redirects the trailing slash at .htaccess not in the foundation application class as it did previously # Redirect Trailing Slashes… RewriteRule ^(.*)/$ /$1 [L,R=301] Just comment it out


3

http and https refer to the protocol in use. http is used for unencrypted cleartext communication, which means transferred data may be intercepted and read in plain by a human. Username/password fields may for instance be captured and read. https refers to ssl/tsl encrypted communication. It must be decrypted to be read. Normally/ideally only the endpoints ...


0

I found the answer here: Allowing users in from an IP address without certificate client authentication The gist of the answer is as follows: <VirtualHost *:443> SSLEngine On SSLProtocol -all +TLSv1 +SSLv3 SSLCipherSuite HIGH:MEDIUM:!aNULL:+SHA1:+MD5:+HIGH:+MEDIUM SSLCertificateFile /etc/ssl/ca/certs/server.crt ...


-1

Try changing the DNS settings on your server to use Google's DNS server at 8.8.8.8. You might be using a managed DNS server like OpenDNS that has policies applied to it.


0

Fedora bug is at https://bugzilla.redhat.com/show_bug.cgi?id=1185708 Cause is curl using NSS, and not wanting to diverge from other NSS using programs. Currently not fixed as of Jul 2015 in Fedora 22


-3

You can use popular Man in the middle attack for this like MITM proxy. And to solve the certificate problem you can deliver certificate directly in active directory environment


4

Do you control the remote server? If you have its private key, you can decrypt the HTTPS data in Wireshark (have tcpdump write to a file with -w then open it in Wireshark). Otherwise, probably your best bet is to pump your traffic through an HTTPS proxy that can decrypt the data - check out Fiddler.


0

I just tried to hit that site from my machine and my firewall blocked it. I am not sure why you want to go to that site but I would make sure that you know what you are doing as it doesn't hit me as a site I would want to go to. :) Can you ping the IPaddress? It resolves to IP Address = 202.76.234.124 Service Provider = GTC MY PIP NET Domain ...



Top 50 recent answers are included