3 ms·

In case anyone else uses Edge, this is what this page looks like on Firefox when you use a VPN https://i.imgur.com/IsvknB2.png https://i.imgur.com/IsvknB2.png

by akerro 8y ago

In case anyone else uses Edge, this is what this page looks like on Firefox when you use a VPN https://i.imgur.com/IsvknB2.png https://i.imgur.com/IsvknB2.png /s PS. wow, what a garbage...

pmontra 8y ago
It's one of those blogs that are implemented as a web app that reads the content with JavaScript, because HTML is not enough... The text is a JSON at https://zsmb.co:8443/public/articledetails/url/on-from-java-to-kotlin-and-back-again https://zsmb.co:8443/public/articledetails/url/on-from-java-... Btw, that 8443 port is probably blocked by firewalls in many enterprise networks. They usually allow only ports 80 and 443.
- zsmb 8y ago
  Hey, site author here. I'll try not to spam too much and just reply to this one comment to address the feedback around here about the technical aspects of the site. - Yes, it's a completely pointless web app in the place of what could be a very simple, quick, and well functioning static HTML site. I'm using it as a hobby project to test drive a framework I'm working on. I do desparately need feedback on it, so thank you for everyone who's reporting issues! - Yes, I didn't have time to do any compatibility testing, so right now I only know that it works alright in Chrome. There are probably things that are very easy to fix (e.g. not using those couple functions that are missing in Edge), I'll have to look into these later. - I don't know if I can solve the port issue yet, I understand that random ports besides 80 and 443 are often blocked, I've actually ran into this just trying to access my own site already too. I only have this one domain and one server for it so far, and I need separate ports to serve the app and to expose the API it talks to. I'll have to think about how I can solve this later.
  - pmontra 8y ago
    From your answer I guess you have a static web server on port 80 and another one on port 8443. The URL of the JSON starts with /public so I guess it's completely static. If you can setup the second web server then you're probably in control of the server. How about reverse proxying an /api URL to localhost:8443? If you can only run another web server on 8443 and can't modify the configuration of the main one on port 80... You simply serve the static JSON file from port 80. This is too easy so you probably can't do that. Do you have an application serving those files on 8443? Maybe run it once to create a file and store it where the web server at port 80 can serve it. Some small script with curl should be enough.

by akerro 8y ago

In case anyone else uses Edge, this is what this page looks like on Firefox when you use a VPN https://i.imgur.com/IsvknB2.png https://i.imgur.com/IsvknB2.png /s PS. wow, what a garbage...

pmontra 8y ago

It's one of those blogs that are implemented as a web app that reads the content with JavaScript, because HTML is not enough... The text is a JSON at https://zsmb.co:8443/public/articledetails/url/on-from-java-to-kotlin-and-back-again https://zsmb.co:8443/public/articledetails/url/on-from-java-... Btw, that 8443 port is probably blocked by firewalls in many enterprise networks. They usually allow only ports 80 and 443.

zsmb 8y ago
Hey, site author here. I'll try not to spam too much and just reply to this one comment to address the feedback around here about the technical aspects of the site. - Yes, it's a completely pointless web app in the place of what could be a very simple, quick, and well functioning static HTML site. I'm using it as a hobby project to test drive a framework I'm working on. I do desparately need feedback on it, so thank you for everyone who's reporting issues! - Yes, I didn't have time to do any compatibility testing, so right now I only know that it works alright in Chrome. There are probably things that are very easy to fix (e.g. not using those couple functions that are missing in Edge), I'll have to look into these later. - I don't know if I can solve the port issue yet, I understand that random ports besides 80 and 443 are often blocked, I've actually ran into this just trying to access my own site already too. I only have this one domain and one server for it so far, and I need separate ports to serve the app and to expose the API it talks to. I'll have to think about how I can solve this later.
- pmontra 8y ago
  From your answer I guess you have a static web server on port 80 and another one on port 8443. The URL of the JSON starts with /public so I guess it's completely static. If you can setup the second web server then you're probably in control of the server. How about reverse proxying an /api URL to localhost:8443? If you can only run another web server on 8443 and can't modify the configuration of the main one on port 80... You simply serve the static JSON file from port 80. This is too easy so you probably can't do that. Do you have an application serving those files on 8443? Maybe run it once to create a file and store it where the web server at port 80 can serve it. Some small script with curl should be enough.