blocks|key|562745|text|现在，您似乎需要一个反向代理来为您管理SSL。我发现一个ticket和一个thread在讨论这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|562746|entityMap|0|LINK|mutability|MUTABLE|url|https://play.lighthouseapp.com/projects/82401-play-20/tickets/215-tls-https-support-in-play-20|1|https://groups.google.com/d/topic/play-framework/DvD8iqmIwE4/discussion^0|S|6|0|11|6|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

Right now you seem to need a reverse proxy managing the SSL for you. I found a <a href="https://play.lighthouseapp.com/projects/82401-play-20/tickets/215-tls-https-support-in-play-20" rel="nofollow">ticket</a> and a <a href="https://groups.google.com/d/topic/play-framework/DvD8iqmIwE4/discussion" rel="nofollow">thread</a> discussing this.

blocks|key|562788|text|设置Play+(2.2.x)的当前版本的文档在这里：http://www.playframework.com/documentation/2.2.x/ConfiguringHttps|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|562789|entityMap|0|LINK|mutability|MUTABLE|url|http://www.playframework.com/documentation/2.2.x/ConfiguringHttps^0|Q|1T|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

The documentation for setting up the current version of Play (2.2.x) is here:
<a href="http://www.playframework.com/documentation/2.2.x/ConfiguringHttps">http://www.playframework.com/documentation/2.2.x/ConfiguringHttps</a>

blocks|key|562846|text|我们做的一件事是使用AWS+ELB来处理我们的SSL，然后使用播放过滤器设置SSL转发(+HTTPS)。它的主要好处是减轻了服务器上的SSL负载，而且您不必在play之前运行Apache或Nginx+(正如一些解决方案指出的那样)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|562847|你可以在这里看到我的答案：https://stackoverflow.com/a/23646948/690164|offset|length|562848|我还在我的博客中写了一些关于它的更多内容：http://www.mentful.com/2014/05/25/play-framework-filter-for-aws-elastic-load-balancer-forward-http-to-https/|562849|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/23646948/690164|1|http://www.mentful.com/2014/05/25/play-framework-filter-for-aws-elastic-load-balancer-forward-http-to-https/^0|0|D|17|0|0|L|30|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

One thing we did was to use AWS ELB to handle our SSL, then setup the SSL forwarding (HTTP -> HTTPS) using a plays filters. The main benefit, takes the SSL load off your server and you don't have to run Apache or Nginx in front of play (as some solution point out).

You can see my answer here:
<a href="https://stackoverflow.com/a/23646948/690164">https://stackoverflow.com/a/23646948/690164</a>

I also write a bit more about it in my blog:
<a href="http://www.mentful.com/2014/05/25/play-framework-filter-for-aws-elastic-load-balancer-forward-http-to-https/" rel="nofollow noreferrer">http://www.mentful.com/2014/05/25/play-framework-filter-for-aws-elastic-load-balancer-forward-http-to-https/</a>

blocks|key|562897|text|我使用的是securesocial+3.03M。设置|type|unstyled|depth|inlineStyleRanges|entityRanges|data|562898|securesocial.ssl+=+true+|code-block|syntax|javascript|562899|在securesocial.conf中，您应该可以运行了。然后使用以下命令重新启动sbt或激活器|562900|JAVA_OPTS=-Dhttps.port=9443+activator+run|562901|转到localhost:9443|562902|尽情享受|562903|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I'm using securesocial 3.0.3M. Set 

<pre><code>securesocial.ssl = true 
</code></pre>

in securesocial.conf and you should be good to go. 
Then restart your sbt or activator with 

<pre><code>JAVA_OPTS=-Dhttps.port=9443 activator run
</code></pre>

Go to localhost:9443

enjoy

blocks|key|562957|text|这对于本地测试https很有用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|562958|activator+"run+-Dhttps.port=9005"|code-block|syntax|javascript|562959|然后将浏览器指向https://localhost:9005。|offset|length|style|CODE|562960|entityMap^0|0|0|8|M|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

This is useful for locally testing https:

<pre><code>activator "run -Dhttps.port=9005"
</code></pre>

Then point your browser to <code>https://localhost:9005</code>.

I've read
<a href="https://stackoverflow.com/questions/5039012/how-to-configure-playframework-server-to-support-ssl">How to configure playframework server to support ssl</a>
and I also tried to follow <a href="http://www.playframework.org/documentation/1.1.1/releasenotes-1.1#https" rel="nofollow noreferrer">http://www.playframework.org/documentation/1.1.1/releasenotes-1.1#https</a> but it doesn't work for me

many thanks~

I read the doc for Play1 because I can't find any more updated information for Play2 about https.

in application.conf, I added these lines:

<pre><code>https.port=9443
certificate.key.file=conf/host.key
certificate.file=conf/host.cert
</code></pre>

I type <code>run</code> in the play console, and try to access the server at <code>https://localhost:9443</code> the browser timed out without anything logged in the console output

How to config PlayFramework2 to support SSL?

服务器

我读过，我也试着关注，但它对我不起作用非常感谢~我阅读了Play1的文档，因为我找不到Play2关于https的更多更新信息。在application.conf中，我添加了以下几行：https.port=9443certificate.key.file=conf/host.keycertificate.file=con...

问如何配置PlayFramework2以支持SSL？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何配置PlayFramework2以支持SSL？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何配置PlayFramework2以支持SSL？
EN