Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backend always error on valid /get_timetable in prod #63

Closed
ixhbinphoenix opened this issue Dec 12, 2023 · 2 comments
Closed

Backend always error on valid /get_timetable in prod #63

ixhbinphoenix opened this issue Dec 12, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@ixhbinphoenix
Copy link
Owner

When a user (that has manually changed the JSESSIONID cookie to apply to both domains) tries requesting their timetable or the lernbüros, the backend server instantly exists with Code 0 without any traces in the logs, not even the request that caused the crash is mentioned. This does not happen in debug builds, where the methods still dont work, but return a 'Untis done fucked up' error instead of instantly exiting.

I will provide logs later today

@ixhbinphoenix ixhbinphoenix added the bug Something isn't working label Dec 12, 2023
@ixhbinphoenix
Copy link
Owner Author

Well for some fucking reason it no longer does this locally. I'm currently changing stuff on the docker image, let's see if that fixes stuff on prod

@ixhbinphoenix
Copy link
Owner Author

Update: Backend no longer crashes, but always returns Untis done fucked up

@ixhbinphoenix ixhbinphoenix changed the title Backend crashes on valid /get_timetable in prod Backend always error on valid /get_timetable in prod Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants