Skip to content

cors/csrf/시간#13

Open
kem0-kem wants to merge 3 commits intoKEEPER31337:developfrom
kem0-kem:fix/cors-csrf-attendance-flow
Open

cors/csrf/시간#13
kem0-kem wants to merge 3 commits intoKEEPER31337:developfrom
kem0-kem:fix/cors-csrf-attendance-flow

Conversation

@kem0-kem
Copy link
Copy Markdown

@kem0-kem kem0-kem commented Mar 28, 2026

cors/csrf/시간

@kem0-kem
Copy link
Copy Markdown
Author

@codex review

@kem0-kem kem0-kem changed the title fix: tighten cors and split attendance creation flow cors/csrf/시간 Mar 28, 2026
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 88d41234a3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Copy link
Copy Markdown
Author

@kem0-kem kem0-kem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

데브서버허용

@kem0-kem
Copy link
Copy Markdown
Author

@codex review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fd5ae7678d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +52 to +53
attendanceService.create(member.getId());
return ResponseEntity.ok(attendanceService.getTodayAttendancePoint(member));
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3 Badge Use one date snapshot for POST /attendances/point flow

createTodayAttendance performs a write and then an immediate read, but the write path (AttendanceService.create) and read path (AttendanceService.getTodayAttendancePoint) each call now separately; if the request crosses midnight between these calls, the attendance can be saved for day N and read for day N+1, causing a false ATTENDANCE_NOT_FOUND right after successful creation. Capture a single date/time once in this endpoint flow (or return created data directly) to avoid the midnight boundary failure.

Useful? React with 👍 / 👎.

@cjaewon
Copy link
Copy Markdown
Member

cjaewon commented Mar 30, 2026

프론트 개발 서버에서 프록시 쓰면 해결되서 localhost cors는 허용할 필요는 없을 것 같습니다.

@chatgpt-codex-connector
Copy link
Copy Markdown

To use Codex here, create a Codex account and connect to github.

@kem0-kem
Copy link
Copy Markdown
Author

프론트 개발 서버에서 프록시 쓰면 해결되서 localhost cors는 허용할 필요는 없을 것 같습니다.

로컬호스트 뺐습니다.

@cjaewon
Copy link
Copy Markdown
Member

cjaewon commented Apr 27, 2026

split attendance creation flow는 뭘 수정하신거에요?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants