Refined proxy setup
13 Feb 2015 12:17:50 UTC
Topic 197969
(moderation:
Hi everyone,
We refined our proxy setup today to increase compatibility with BOINC's web code. Please let us know when you find any webpages not loading properly or web resources missing.
Thanks,
Oliver
Einstein@Home Project
Refined proxy setup
)
Fonts are larger in the forum menues, not in the posts themselves.
Everything else looks the same so I don't think the whole CSS file is missing. Maybe you made changes in it?
I'm using Firefox on windows
Edit: Just noticed the info box to the left of posts also have a larger font for the name. Maybe always been like that, can't remember
There are some odd characters
)
There are some odd characters (Â) on the server status page.
RE: Fonts are larger in the
)
Yep, noticed that myself already. We haven't touched the CSS but the proxy now processes the HTML itself and might even "fix" broken HTML. I need to have a look at the original code and compare the details.
Oliver
Einstein@Home Project
RE: There are some odd
)
Not for me. Where exactly do you see them?
Thanks,
Oliver
PS: I do see two extra non-breaking spaces though. This is due to the auto-fixes alluded to above. Will fix them...
Einstein@Home Project
RE: There are some odd
)
There are 3 such characters in Firefox on the status page. They are in "Project daemons", ProgramÂ, and one is hanging to the far right of the status page above the "Workunits and tasks" line.
Ah, in FF I do see them
)
Ah, in FF I do see them myself. These are likely anchors. I'll look into it...
Einstein@Home Project
Actually there are 12! Just
)
Actually there are 12! Just scroll further down ;)
Yep, all the same. In fact,
)
Yep, all the same. In fact, this is caused by the content type header of the server response not being set correctly and the nbsp;'s used for invisible anchors get interpreted as latin1 instead of utf8. The root cause seems to be a flawed mod_cache module in conjunction with some backend requests temporarily failing via VPN.
You see, a rather complex issue this time. Glad it's just cosmetic so far. We'll look into it by I don't think we'll fully resolve it before the weekend. In the meantime I've deactivated the cache as a workaround. Performance seems still fine to me...
Note: this doesn't relate to the font-size changes. That still needs to be investigated...
Oliver
Einstein@Home Project
The larger font size is used
)
The larger font size is used for the private message inbox, as well as the two places previously mentioned.
Ok, font sizes back to normal
)
Ok, font sizes back to normal :-)
Background: the proxy setup we use now parses any HTML content returned from the backend. Clean HTML doesn't need any special care but BOINC's stock web code does: I inadvertently slightly changed DOCTYPE declaration. That put the pages into quirks-mode which, for instance, means that some body CSS rules (like font-size) are not inherited by tables, which causes them to use the initial size of 1em/16px. Gotcha. I could fix it by adding the loose.dtd specification back to the DOCTYPE.
Oliver
Einstein@Home Project