Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Is it possible to set the Server Base URL to support both HTTP and HTTPS?


We are setting up Confluence purely for the Team Calendar add-in as we have a split team across O365 and Google, and it seems impossible to get the native shared team calendars to sync with each other without breaking other things.

I have configured everything to come in via HTTPS which is great, but according to this article ( Google doesn't support HTTPS so users do not see the Add to Google Calendar link. I’m not sure if this then leads to reduced functionality for Google users (i.e. one-way instead of two-way synchronisation), but if it does, is there a way to be able to provide both HTTP and HTTPS access on the base URL?

Currently, the Server Base URL is set to use HTTPS, so although I can view the site using HTTP, as soon as you view a calendar, all you see is a spinning wheel. If the functionality is the same in either case, this I suppose this is a moot point.


1 answer

To answer my own question, it looks like these subscriptions are only a one-way thing, even in Google. I guess the Add to Google Calendar button is merely a way to ease this for the user. I do have a question regarding two-way synchronisation in O365 (see, but I guess this is not something that could happen. This means that the need for HTTP becomes a littel less relevant.

On another note, it would appear as if the spinning wheel on the calendar is due to the line added to the server.xml for the Nginx Proxy. If I set is as:

proxyName="" proxyPort="443" scheme="https"

All works fine for HTTPS, and if I set it as:

proxyName="" proxyPort="80" scheme="http"

All works fine for HTTP, but I’m not sure if you can have both.  

Suggest an answer

Log in or Sign up to answer
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

82 views 0 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you