I'm assuming you opened the inspector / dev tools, went to the network tab, and selected one of the requests that had a content-length mismatch error, and this is what was in the "response" (raw) area off to the right.
What was the URL for this request? The actual response here is the output of index.xjs, or the home/default page of your site. If the request was not for '/' or for 'index.xjs' then we'll need to find out why your server sent this.
I made an interesting discovery. This contorted website seemingly occurs only if I try to access my local IP address from the host device on my local network. For instance, I'm accessing the website from my phone right now through my local IP address with no issues. Everything looks normal.
This has been my understanding of the problem all along. Or I think I was under the impression that you were viewing your website from a browser on the server itself.
Sorry, I have no new ideas at this time.
This has been my understanding of the problem all along. Or I think I was under the impression that you were viewing your website from a browser on the server itself.
Sorry, I have no new ideas at this time.
This has been my understanding of the problem all along. Or I think I was under the impression that you were viewing your website from a browser on the server itself.
Sorry, I have no new ideas at this time.
well, i've routed the traffic through the public ip address for now until
i
can figure this out. kinda defeats the purpose of a closed circuit system, but it will work for now. i appreciate all of your help.
well you are doing something out of the ordinary, so you can expect to have issues. we also don't know what you could possibly have done wrong. i've seen it 100 times. people say they dont do anything special and then it ends up being operator error.
look around and find your solution. sometimes the only person who can help you is you, because you're the guy behind the wheel.
SYS64738 wrote to MRO <=-
look around and find your solution. sometimes the only person who can help you is you, because you're the guy behind the wheel.
Well, I'm beginning to think that is the case. It's weird to have an issue that you can't see where anyone has discussed it before. I'm
sure someone else has had this problem, but for the life of me I can't find where they discussed it at all.
Not sure if this makes any difference at all, but 127.0.0.1 and my
locally assigned ip (192.168.0.1) bother produce the same result. Part
of me suspects that it has something to do with the router. I dunno.
Back to the drawing board.
Not sure if this makes any difference at all, but 127.0.0.1 and my locally assigned ip (192.168.0.1) bother produce the same result. Part
That's because those addresses are the same thing in reality. They both point to the local machine.
Digital Man wrote to Gamgee <=-
Re: Re: website issues with 127.0.0.1
By: Gamgee to SYS64738 on Sat Nov 23 2024 08:23 am
Not sure if this makes any difference at all, but 127.0.0.1 and my locally assigned ip (192.168.0.1) bother produce the same result. Part
That's because those addresses are the same thing in reality. They both point to the local machine.
Not necessarily. 192.168.* just means "private address" (as in private network), does not mean "localhost" as 127.* does.
That's because those addresses are the same thing in reality. They both point to the local machine.
It almost certainly does have something to do with the router. Google
up the term "hairpinning" as it relates to routers.
| Sysop: | Sys |
|---|---|
| Location: | Otteveny, Hungary |
| Users: | 7 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 17:49:53 |
| Calls: | 15 |
| Calls today: | 15 |
| Files: | 34 |
| U/L today: |
10 files (225M bytes) |
| D/L today: |
7 files (64,431K bytes) |
| Messages: | 3,481 |
| Posted today: | 5 |