Fix/178 AccessToken의 Bearer 키워드 문제 해결 #179
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- 쿠키는 인코딩없이 절대로 띄어쓰기가 들어갈 수 없음.
- Authorization 헤더에 Bearer 키워드가 있을 경우, 접두사를 제거하여 처리. - Bearer 키워드가 없는 경우, 그대로 처리. - 클라이언트의 다양한 요청 형식을 수용하도록 개선.
1 task
|
7zrv
approved these changes
Dec 7, 2024
leebs0521
approved these changes
Dec 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolved :
📌 과제 설명
AccessToken을 쿠키에 설정해 줄 때, httpOnly로 설정되어 프론트에서 이를 헤더에 담을 수만 있고 Prefix를 설정할 수 없습니다.
Bearer 키워드(공백 유의)가 문제가 되는데 이를 JwtFilter에서 핸들링하겠습니다.
👩💻 요구 사항과 구현 내용
✅ PR 포인트 & 궁금한 점
Bearer키워드가 설정될 수 없습니다. 띄어쓰기가 있는 것이 쿠키 정책에 올바르지 않아서 인코딩이 필요했고, 이를 해결하기 위해서 prefix 조건문을 추가했습니다.