MIYAGI Hikaru ddd0bb69e1 Merge HIDDEN_SERVICE_VIA_TRANSPARENT_PROXY into ALLOW_ACCESS_TO_HIDDEN_SERVICE (#7901) ... If Mastodon accesses to the hidden service via transparent proxy, it's needed to avoid checking whether it's a private address, since `.onion` is resolved to a private address. I was previously using the `HIDDEN_SERVICE_VIA_TRANSPARENT_PROXY` to provide that function. However, I realized that using `HIDDEN_SERVICE_VIA_TRANSPARENT_PROXY` is redundant, since this specification is always used with `ALLOW_ACCESS_TO_HIDDEN_SERVICE`. Therefore, I decided to integrate the setting of `HIDDEN_SERVICE_VIA_TRANSPARENT_PROXY` into` ALLOW_ACCESS_TO_HIDDEN_SERVICE`.		2018-06-29 15:36:02 +02:00
..
environments
initializers	Merge HIDDEN_SERVICE_VIA_TRANSPARENT_PROXY into ALLOW_ACCESS_TO_HIDDEN_SERVICE (#7901)	2018-06-29 15:36:02 +02:00
locales	Keyword/phrase filtering (#7905)	2018-06-29 15:34:36 +02:00
webpack
application.rb
boot.rb
brakeman.ignore
database.yml
deploy.rb
environment.rb
i18n-tasks.yml
navigation.rb	Keyword/phrase filtering (#7905)	2018-06-29 15:34:36 +02:00
puma.rb
routes.rb	Keyword/phrase filtering (#7905)	2018-06-29 15:34:36 +02:00
secrets.yml
settings.yml
sidekiq.yml
themes.yml
webpacker.yml