blocks|key|16312|text|谢谢你的帮助。我真的不知道它是如何工作的，但现在它可以工作了！我不记得我到底做了什么，但最后一次是像这样修改我的000-default-le-ssl.conf文件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|16313|SSLProxyEngine+On
SSLProxyVerify+none+
SSLProxyCheckPeerCN+off
SSLProxyCheckPeerName+off
SSLProxyCheckPeerExpire+off
<Location+/api>
++++ProxyPass+http://127.0.0.1:3000/api/
++++ProxyPassReverse+http://127.0.0.1:3000/api/
++++ProxyPass+https://127.0.0.1:3000/api/
++++ProxyPassReverse+https://127.0.0.1:3000/api/
</Location>|code-block|syntax|javascript|16314|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Thanks for your help. I don't really know how but it works now!
I dont rember exactly what i did, but the last one was to modify my 000-default-le-ssl.conf file like this:

<pre><code>SSLProxyEngine On
SSLProxyVerify none 
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
SSLProxyCheckPeerExpire off
&lt;Location /api&gt;
 ProxyPass http://127.0.0.1:3000/api/
 ProxyPassReverse http://127.0.0.1:3000/api/
 ProxyPass https://127.0.0.1:3000/api/
 ProxyPassReverse https://127.0.0.1:3000/api/
&lt;/Location&gt;
</code></pre>

blocks|key|16316|text|你自己找到的解决方案在我看来很奇怪。您打开SSLProxyEngine，然后禁用所有安全措施。后端API是否在端口3000同时运行HTTPS和HTTP？这是不可能的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|16317|我经常使用这个设置(apache作为后端应用程序的代理)，并建议使用以下配置：|16318|因为我不理解重写指令的目的，所以我省略了它们。端口80上的VirtualHost总是将HTTP请求重定向到HTTPS。如果这样可以将permanent添加到指令中(某些浏览器会缓存永久，请参阅VirtualHost+*：80中的注释)。|offset|length|style|CODE|16319|HTTPS的VirtualHost提供来自/var/www/html的DocumentRoot的内容。Directory指令负责只为正确寻址的文件提供服务(不可能进行查找)。VirtualHost还为同一台服务器上的端口3000上的/api提供代理。|16320|如果你的letsencrypt配置是正确的(填写XXXX)，它应该适用于Apache2.4。这两个站点配置都可以写入到单个文件中，该文件通常位于/etc/apache2/+VirtualHost+-可通过一个指向启用/etc/apache2/site的符号链接获得。在测试此配置之前，请删除/重命名.htaccess文件和其他配置。如果您需要通过apache进行访问控制，也可以直接在VirtualHost配置中进行配置。|16321|<VirtualHost+*:80>
++++ServerName+XXXX.ddns.net
++++#+Always+https
++++Redirect+/+https://XXXX.ddns.net/
#++++Redirect+permanent+/+https://XXXX.ddns.net/
</VirtualHost>

<VirtualHost+*:443>
++++ServerAdmin+webmaster@localhost
++++ServerName+XXXX.ddns.net
++++#+These+are+your+SSL+settings;+your+responsibility
++++SSLCertificateFile+/etc/letsencrypt/live/XXXX.ddns.net/fullchain.pem
++++SSLCertificateKeyFile+/etc/letsencrypt/live/XXXX.ddns.net/privkey.pem
++++Include+/etc/letsencrypt/options-ssl-apache.conf

++++#+Your+document+root;+where+the+JavaScript+application+lives
++++DocumentRoot+/var/www/html
++++<Directory+/var/www/html/+>
++++++++Options+-Indexes+%2BFollowSymLinks+-MultiViews
++++++++AllowOverride+None
++++++++Order+Allow,Deny+
++++++++Allow+From+All
++++</Directory>

++++#+Reverse+proxy+settings+for+api
++++ProxyRequests+++++Off
++++ProxyPreserveHost+On
++++<Location+/api+>
++++++++ProxyPass++++++++http://127.0.0.1:3000/api
++++++++ProxyPassReverse+http://127.0.0.1:3000/api
++++</Location>
</VirtualHost>|code-block|syntax|javascript|16322|entityMap^0|0|0|1U|9|0|1F|9|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@$F|X|G|Y|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|Z|8|@$F|10|G|11|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|12|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|13|8|@]|9|@]|A|$Q|R]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

Your self-found solution looks strange to me. You switch on the SSLProxyEngine and than disable all security measures. Is the backend API running under HTTPS and HTTP at port 3000 at the same time? This is not possible. 

I use this setup (apache as proxy to backend application) pretty often and would suggest the following configuration:

As I did not understand the purpose of the rewrite directives I left them out. The VirtualHost at port 80 always redirects HTTP requests to HTTPS. If this works add <code>permanent</code> to the directive (permanent is cached by some browsers, see comment in VirtualHost *:80). 

The VirtualHost for HTTPS serves content from your DocumentRoot at /var/www/html. The <code>Directory</code> directive takes care that only correctly addressed files are served (no lookups possible). The VirtualHost also provides the proxy for the /api on the same server on port 3000. 

It should work for apache 2.4 if your letsencrypt configuration is correct (fill-in the XXXX). Both VirtualHost configurations can be written into a single file, usually located in /etc/apache2/sites-available with a symlink to /etc/apache2/sites-enabled. Please remove/rename your .htaccess file and other configurations before testing this configuration. If you need access control through apache this could also be configured directly in the VirtualHost configuration. 

<pre><code>&lt;VirtualHost *:80&gt;
 ServerName XXXX.ddns.net
 # Always https
 Redirect / https://XXXX.ddns.net/
# Redirect permanent / https://XXXX.ddns.net/
&lt;/VirtualHost&gt;

&lt;VirtualHost *:443&gt;
 ServerAdmin webmaster@localhost
 ServerName XXXX.ddns.net
 # These are your SSL settings; your responsibility
 SSLCertificateFile /etc/letsencrypt/live/XXXX.ddns.net/fullchain.pem
 SSLCertificateKeyFile /etc/letsencrypt/live/XXXX.ddns.net/privkey.pem
 Include /etc/letsencrypt/options-ssl-apache.conf

 # Your document root; where the JavaScript application lives
 DocumentRoot /var/www/html
 &lt;Directory /var/www/html/ &gt;
 Options -Indexes +FollowSymLinks -MultiViews
 AllowOverride None
 Order Allow,Deny 
 Allow From All
 &lt;/Directory&gt;

 # Reverse proxy settings for api
 ProxyRequests Off
 ProxyPreserveHost On
 &lt;Location /api &gt;
 ProxyPass http://127.0.0.1:3000/api
 ProxyPassReverse http://127.0.0.1:3000/api
 &lt;/Location&gt;
&lt;/VirtualHost&gt;
</code></pre>

I have a problem to redirect some request to an other port. Here's my configuration:

<ul>
<li>I have a public domain like XXXX.ddns.net </li>
<li>I have a Rapsbian server with apache and files in my /var/www folders are correctly served (angular website)</li>
<li>On the same Raspbian server there is a REST server running on the 3000 port </li>
<li>This is running on HTTPS with SSL(letsencrypt)</li>
</ul>

I would like that all requests to XXXX.ddns.net/api/* to be redirected to the 3000 port.

I change the .htaccess file and the rewrite rule seems to works on local but I can't make it working from my internet site. API requests achieve with a error 500.

Here is my current .htaccess file:

<pre><code>RewriteEngine On
RewriteRule ^api/(.*) https://localhost:3000/api/$1 [QSA]
# not sure if it should be http or https in the rule but nothing works
#RewriteRule ^api/(.*) http://localhost:3000/api/$1 [QSA]

# If an existing asset or directory is requested go to it as it is
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} -f [OR]
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} -d
RewriteRule ^ - [L]

# If the requested pattern is file and file doesn't exist, send 404
RewriteCond %{REQUEST_URI} ^(\/[a-z_\-\s0-9\.]+)+\.[a-zA-Z]{2,4}$
RewriteRule ^ - [L,R=404]
</code></pre>

Here is my current 000-default-le-ssl.conf file (in /etc/apache2/sites-available):

<pre><code>&lt;IfModule mod_ssl.c&gt;
&lt;VirtualHost *:443&gt;

 ServerAdmin webmaster@localhost
 DocumentRoot /var/www/html

ServerName XXXX.ddns.net
SSLCertificateFile /etc/letsencrypt/live/XXXX.ddns.net/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/XXXX.ddns.net/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
&lt;Location /api&gt;
 ProxyPass http://127.0.0.1:3000/api
 ProxyPassReverse http://127.0.0.1:3000/api
&lt;/Location&gt;

&lt;/VirtualHost&gt;
&lt;/IfModule&gt;
</code></pre>

If someone could help me to achieve it... 
Thanks!

Redirect specifc HTTPS request to a specific port with apache

服务器

Raspbian

我在将一些请求重定向到其他端口时遇到了问题。下面是我的配置：我有一个像XXXX.ddns.net 这样的公共域我有一台安装了apache的Rapsbian服务器，我的/var/www文件夹中的文件都得到了正确的服务(angular网站)在同一台Raspbian服务器上有一台REST服务器在3000端口上运行这是在带Ra...

问使用apache将指定HTTPS请求重定向到特定端口
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用apache将指定HTTPS请求重定向到特定端口EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用apache将指定HTTPS请求重定向到特定端口
EN