[ZEPPELIN-6494] Use HTTPS for zeppelin.apache.org links in UI#5299
Merged
Conversation
The Angular and classic UIs still linked to the Zeppelin website over http://. The public site serves HTTPS, so switch the home/about UI links to https:// and update the focused E2E expectation that pinned the old scheme for the community link. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ParkGyeongTae
approved these changes
Jul 14, 2026
ParkGyeongTae
left a comment
ParkGyeongTae
left a comment
Member
There was a problem hiding this comment.
LGTM. All UI-facing zeppelin.apache.org links (7 occurrences across the 5 files listed in ZEPPELIN-6494) are correctly switched to HTTPS, and the E2E expectation is updated to match. The one failing CI job is an unrelated flaky Selenium auth test. Thanks for the contribution!
Member
|
Merged into master (9b66912). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this PR for?
The Zeppelin UI still contained several direct
http://zeppelin.apache.orglinks. The public Zeppelin site is served over HTTPS, and newer links in the codebase already use HTTPS. This PR switches the UI-facing website links fromhttp://tohttps://and updates the focused E2E expectation that pinned the old scheme.Changes (5 files, 7 links):
zeppelin-web-angular/src/app/pages/workspace/home/home.component.html— documentation & community linkszeppelin-web-angular/src/app/share/about-zeppelin/about-zeppelin.component.html— "Get involved!" linkzeppelin-web-angular/e2e/tests/home/home-page-external-links.spec.ts— community-link expectationzeppelin-web/src/app/home/home.html— documentation & community links (classic UI)zeppelin-web/src/components/navbar/navbar.html— "Get involved!" link (classic UI)Non-Zeppelin links (e.g.
www.apache.org/licenses/LICENSE-2.0), version placeholders, and unrelated docs are intentionally left unchanged.What type of PR is it?
Improvement
What is the Jira issue?
ZEPPELIN-6494
How should this be tested?
http://zeppelin.apache.orgremains:cd zeppelin-web-angular && npm run lint— passes with no errors.Questions: