-
-
Notifications
You must be signed in to change notification settings - Fork 402
update java-errors.data
#4073
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
Comments
We already have a Ultimately, there's no "correct" list of exceptions to detect, but I think it's a good idea to extend the list. Id be careful with some of the HTTP related exceptions though. In badly configured environments those could be part of genuine error responses that we wouldn't want to block at PL 1. |
This is about updating |
Any updates on this, or should I add this to the Meeting Agenda? |
I like your idea of using regexes. Instead of having to maintain a huge list, we can break it down to a couple of simple patterns. And, as you say, that would also allow us to block packages easily. Can you prepare a draft PR that we could discuss in the chat? |
This issues is for creating a PR with the provided data. Once a decision is made whether we should use regex or pmFromFile, it's very easy for anyone to implement a PR that'll close both issues. |
@Xhoenix did you get around to creating that PR? |
@theseion I'm waiting for a decision to be made on this. |
I understand. As I wrote above, I believe a draft PR would help the discussion, since people would see how it could look in the future. |
Source: ChatGPT
🛑 Critical Java Exceptions That May Appear in HTTP Responses
1️⃣ Java Core Exceptions
2️⃣ Servlet & Web Container Exceptions (Tomcat, Jetty, JBoss, WildFly, WebSphere)
3️⃣ Spring Framework & Spring Boot Exceptions
4️⃣ Database & Hibernate/JPA Exceptions
5️⃣ RMI (Remote Method Invocation) & JNDI Exceptions
6️⃣ Security & Authentication Exceptions
7️⃣ JSON/XML & Serialization Exceptions
8️⃣ Network & IO Exceptions
9️⃣ REST API & HTTP Client Exceptions
I think creating a new rule with a regex assembly file like the following will be better(feel free to improve the regex)
Another way is to block responses containing package names like
java.lang
,javax.servlet
,org.springframework
,org.hibernate
, etc.Note: These LLMs provide disclaimer that the provided info can be wrong, so any suggestions are welcome. 😄
Disclaimer: This ain't an April Fool's joke. 😅
The text was updated successfully, but these errors were encountered: