tum-dev / tum.sexy Goto Github PK

The page https://hunger.tum.sexy/ shows currently several messages, that there were errors while fetching the data.

Further, I would suggest adding the EAT-API webpage to this page (https://tum-dev.github.io/eat-api/).

See screenshot (iOS 15.0.1).

If you search for this room it will go to 404 Not found, which it should not.
Room to find:

02.07.023, Seminarraum (Inf. 2/5) (5607.02.023)

https://nav.tum.sexy/search/02.07.023,%20Seminarraum%20(Inf.%202/5)%20(5607.02.023)

This is what works:

02.07.023, Seminarraum (Inf. 2 5) (5607.02.023)

https://nav.tum.sexy/search/02.07.023,%20Seminarraum%20(Inf.%202%205)%20(5607.02.023)

Problem is /. But encoding doesnt help:

https://nav.tum.sexy/search/02.07.023,%20Seminarraum%20(Inf.%202%2F5)%20(5607.02.023)

Many libraries use + in the query string to encode space. It would be nice if nav.tum.sexy/search/ could support that too.

Typically when entering an unknown subdomain (e.g. https://abc.tum.sexy) you are redirected to https://tum.sexy.

But for keys that start with an m (trigger moodle redirect) and then fallback to original value, they are not redirected. Neither to https://tum.sexy nor to the page without m.

For example visiting https://msp.tum.sexy/ displays

Warning: Undefined array key "moodle_id" in /var/www/html/redirect/routes.php on line 815

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/redirect/routes.php:815) in /var/www/html/redirect/index.php on line 5

the same happens for https://masp.tum.sexy/.

But they should redirect to https://sp.tum.sexy/ and https://asp.tum.sexy respectively.

I believe I know the cause of the error and will create a PR shortly.

sp.tum.sexy points to
https://www.in.tum.de/in/fuer-studierende/bachelor-studiengaenge/informatik/studienplan/studienbeginn-ab-wise-202122/
but it should be
https://www.in.tum.de/in/fuer-studierende/bachelor-studiengaenge/informatik/studienplan/studienbeginn-ab-wise-2021-22/

When using the search, results can not be pinned.

System: Windows 11 pro
Microsoft Edge
Version 118.0.2088.33 (Official build) beta (64-bit) (for the bing chatbot if you know what I mean)

Steps to reproduce:

1. pin one time
2. refresh page
3. pin one second time
4. remove one pin
5. try to pin

Current Behaviour:
I am able to pin the element the second time and I now see it two times pinned (that should be not possible). Then when removing one pin both get removed. And after that I am not able to pin the same element

Expected:
Only possible to pin one time, and after unpinning to pin once again.

For some URLs like mai.tum.sexy (redirecting to Grundlagen KI)we redirect, despite this not being in the list of redirects.
It is not transparent to me, where this behaviour comes from.
This needs looking into, but is not high priority

tum.sexy/pret/ is not working correctly anymore.
The background and some effects seem to load fine but the images and music is missing.

Tested with Chrome 101.0.4951.6, Safari 15.5 and Firefox 100.0.2

https://shop.tum.de/accessoires/extras/105/tum-kondom
Verlinkt auf diese Seite, aber nicht mehr aktuell

Following up on #96 - I now dug into the issue a bit deeper (as I am receiving an SSL certiciate error on macOS as well, not just iOS). I It really seems to be connected to a cached certificate - but the root issue is that the webserver is not sending intermediate certificates.

So this is an issue that should be fixed on the tum.sexy web server.

The issue is quite well explained here: https://community.letsencrypt.org/t/my-iphone-seems-to-used-a-cached-version-of-the-old-expired-r3/160931/2

[..] but a likely cause is because your server doesn't send the intermediate certificates. This causes clients to fetch them themselves and may lead to what you're seeing.

You can verify the issue e.g. on https://www.sslchecker.com/sslchecker (see screenshot):

You should also be able to verify the issue by running openssl s_client -connect tum.sexy:443 (currently returns unable to verify the first certificate, at least for my computer).

Which web server & config are you using? Happy to assist 😊

Let's Encrypt's old root certificate expired on September 30, 2021. As a result, the https://tum.sexy certificate is no longer valid on devices with older CA trust versions. You can find more information here: https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/.

As most links we provide are not relevant to all students and therefore hidden it would be nice to find them through the search functionality at least.

Example: med2.tum.sexy is a valid redirect but only users who went through the source will know that it even exists.

Since @mammuth (btw. thank's for the lovely work in the past!) transfered this repository to TUM-Dev, the "hall of fame" in README.md (see 3b01c90) doesn't work anymore.
I suggest creating a new sourcerer.io account and updating the links.

Cheers!

It looks like all links are currently 404ing, e.g. https://tum.sexy, https://sp.tum.sexy/ etc.
Maybe something with a recent deployment went wrong?