msgbyte / msgbyte/tianji

Custom domain renders a white page

Open
#257 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
3.1k
Forks
194
Avg merge
18m
Merged PRs (30d)
3

Description

Hi there.

I added a custom domain to a status page under the path /status/test, but when I try to see it, it just renders a white page.

On Docker logs I can see that:

tianji-1 STDOUT GET /status/test 200 130 - 0.456 ms
tianji-1 STDOUT GET /status/test 304 - - 0.575 ms

And the browser shows me that it tries to load an iframe with https://CUSTOM.URL/status/test

<html>
    <head></head>
    <body style="padding: 0; margin: 0;">
        <iframe style="border: none; width: 100%; height: 100%;" title src="/status/test">
            -#document (https://CUSTOM.URL/status/test)
                <htmL>
                    <head></head>
                    <body style="padding: 0; margin: 0;">
                        <iframe style="border: none; width: 100%; height: 100%;" title src="/status/test">
                            #document (https://CUSTOM.URL/status/test)
                                <htmL>
                                    <head></head>
                                    <body style="padding: 0; margin: 0;">
                                        <iframe style="border:none; width: 100%; height: 100%;" title src="/status/test">
                                            #document (about:blank)
                                                <html>
                                                    <head></head>
                                                    <body></body>
                                                </html>
                                            "</body>"
                                        </iframe>
                                    </body>
                                </html>
                            "</body>"
                        </iframe>
                    </body>
                </html>
            "</body>"
        </iframe>
    </body>
</html>

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the custom-domain request for /status/test and inspect the rendered iframe behavior in the frontend entry point handling that route. The fix is complete when the custom domain renders the status page once instead of recursively embedding itself and producing a white page.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.