-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should not depend on deployment on root context #1202
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,9 @@ | ||
<title>Jitsi Meet</title> | ||
<meta property="og:title" content="Jitsi Meet"/> | ||
<meta property="og:image" content="/images/jitsilogo.png?v=1"/> | ||
<meta property="og:image" content="images/jitsilogo.png?v=1"/> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @guusdk I think you should fix this by setting:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I typically try to avoid the Additioally, I did not want to add them here, as I dislike how this adds a reference to a specific domain and context (although I believe that the I don't really see an upside to having There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is deployment specific we use, but basically a way to serve the index from one place and rest of the code from a CDN, you can check that in current meet. |
||
<meta property="og:description" content="Join a WebRTC video conference powered by the Jitsi Videobridge"/> | ||
<meta description="Join a WebRTC video conference powered by the Jitsi Videobridge"/> | ||
<meta itemprop="name" content="Jitsi Meet"/> | ||
<meta itemprop="description" content="Join a WebRTC video conference powered by the Jitsi Videobridge"/> | ||
<meta itemprop="image" content="/images/jitsilogo.png?v=1"/> | ||
<link rel="icon" type="image/png" href="/images/favicon.ico?v=1"/> | ||
<meta itemprop="image" content="images/jitsilogo.png?v=1"/> | ||
<link rel="icon" type="image/png" href="images/favicon.ico?v=1"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@guusdk why do you need this change? Can't you handle this in your webserver's configs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am actually not using SSI at all - I cannot process them in my webserver. I assumed, perhaps incorrectly, that making the reference relative to the file makes for a safer inclusion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have access to the jetty that you are using, can you add some handlers there? I cannot remember can this be added runtime or handlers are setup on startup of jetty...