Skip to content
This repository has been archived by the owner on Feb 24, 2024. It is now read-only.

PostgREST Planner - Document "pool protection" from bad HTTP logic #557

Closed
steve-chavez opened this issue Jul 11, 2022 · 2 comments
Closed

PostgREST Planner - Document "pool protection" from bad HTTP logic #557

steve-chavez opened this issue Jul 11, 2022 · 2 comments
Labels
references Technical reference.

Comments

@steve-chavez
Copy link
Member

Not sure what to call PostgREST/postgrest#1094 and PostgREST/postgrest#2364, but I believe those are a security feature.
@steve-chavez steve-chavez added the references Technical reference. label Jul 11, 2022
@steve-chavez steve-chavez mentioned this issue Jul 11, 2022
Open
@steve-chavez
Copy link
Member Author

Taking the ideas on PostgREST/postgrest#1804, I realize now that we actually have a planner that acts before we use a database connection.

We should refactor the modules and then have an explanation for this on the docs.

@steve-chavez steve-chavez changed the title Document "pool protection" from bad HTTP logic Document "pool protection" from bad HTTP logic(PostgREST Planner) Sep 19, 2022
@steve-chavez steve-chavez changed the title Document "pool protection" from bad HTTP logic(PostgREST Planner) PostgREST Planner - Document "pool protection" from bad HTTP logic Sep 19, 2022
@wolfgangwalther
Copy link
Member

Seems like this would be covered by #348

@wolfgangwalther wolfgangwalther closed this as not planned Won't fix, can't repro, duplicate, stale Feb 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
references Technical reference.
Milestone
No milestone
Development

No branches or pull requests
2 participants
@steve-chavez @wolfgangwalther