prestodb/presto

Incorrect HTTP response code 500 is returned when the password is too long

Open

#25,679 创建于 2025年8月4日

在 GitHub 查看
 (4 评论) (0 反应) (0 负责人)Java (15,558 star) (5,240 fork)batch import
buggood first issue

描述

When file-based authentication is enabled, and the password is too long, the server responds with HTTP 500, not the expected HTTP 401

Your Environment

  • Presto version used: 0.294-SNAPSHOT
  • Storage (HDFS/S3/GCS..):
  • Data source and connector used:
  • Deployment (Cloud or On-prem): on-prem with Docker Swarm
  • Pastebin link to the complete debug logs: https://pastebin.com/SvU1KCpQ

Expected Behavior

The server should return HTTP 401.

Current Behavior

The server should return HTTP 401.

Possible Solution

Catch the RuntimeException and wrap it into a PrestoException.

Steps to Reproduce

Screenshots (if appropriate)

Context

贡献者指南

技术栈
java
领域
backend
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
JavaBasic Presto architecture
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
75
研究方向
The issue is about file based authentication returning 500 instead of 401. The fix involves catching RuntimeException and wrapping it into a PrestoException. Look at the authentication related classes under presto main/src/main/java/com/facebook/presto/server/security/ or similar. The PrestoException class can be found in presto spi. There are comments in the issue suggesting the approach. Ensure the fix returns 401 for bad password length rather than 500.