Skip to content
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

Custom parameter names must be two or more simple identifiers separated by dots.","code":"42602" #1971

Closed
lduguid opened this issue Oct 1, 2021 · 3 comments

Comments

@lduguid
Copy link

lduguid commented Oct 1, 2021

Environment

  • PostgreSQL version: 14.0
  • PostgREST version: 8.0
  • Operating system: Windows 10 Pro

Description of issue

followed instructions on https://postgrest.org/en/v8.0/tutorials/tut0.html . Not using docker image but previuosly installed PostgreSQL 14.0 server, which runs as intended in all other respects as far as I can tell. After starting PostgREST with this conf.

db-uri			= "postgres://authenticator:mysecretpassword@localhost:5433/postgres"
db-schema		= "api"
db-anon-role	= "web_anon"
server-host		= "!4"
server-port		= 43000
log-level		= "info"

I have applied the various db-anon-roll and schema etc. as outlined in tutorial. It all appears OK. However when I navigate to the URI -> http://192.168.50.140:43000/ (also used localhost and 127.0.0.1 etc.) I get these responses;

{"hint":null,"details":"Custom parameter names must be two or more simple identifiers separated by dots.","code":"42602","message":"invalid configuration parameter name \"request.header.upgrade-insecure-requests\""}

[Refresh]

{"hint":null,"details":"Custom parameter names must be two or more simple identifiers separated by dots.","code":"42602","message":"invalid configuration parameter name \"request.header.cache-control\""}

Client does not appear to matter, Chrome, Firefox, CURL, PostWoman etc.

I am not sure if it is a bug per se or some misconfiguration on my side but some guidance on what to do next would be

image

image

image

image

image
appreciated.

@bnjmnt4n
Copy link

bnjmnt4n commented Oct 1, 2021

This is a breaking change that Postgres v14 introduced, and PostgREST is not compatible with v14 yet. See #1857.

@lduguid
Copy link
Author

lduguid commented Oct 1, 2021

thanks for the heads up. Did you want me to close this issue as it has been recorded and commented appropriately else where?

@steve-chavez
Copy link
Member

@lduguid Yeah, let's continue on #1857. Btw, there's also a fix in progress #1968. We'll make a new release when that's merged.

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

No branches or pull requests

3 participants