Table not found

[vmgonzalez1990]

I have a database with several personalized schemes. Everyone is exposed to the API, I can get tables and views, however I can not make posts to the tables. I only get the error in response:

localhost:3000/table not found

[laurenceisla]

How are you doing the request? Is it with a curl or a js client? Please add the POST example and the exact error you're getting to better debug the issue.

[vmgonzalez1990]

I'm doing it through an http call from an app.

function insertRow(schema, table, dict) {
        HttpRequest        
        .post(String('http://%1/rest/v1/%2').arg(config.projectId).arg(table))
        .set('apikey', config.apiKey)
        .set('Accept-Profile', schema)
        .set('Content-Type', 'application/json')
        .set('Prefer', 'return=minimal')
        .send(dict)
        .then(function(res) {
            HttpStatusCodes.validateStatusCodes(res.status)
            if (res.status === 201) {
                insertedRow(true, 'Inserted row success')
            }
        })
        .catch(function(err) {console.debug(err)
            insertedRow(false, 'Failed to inserted row')
        });
    }

Server response:

Error: Error transferring http://localhost:8000/rest/v1/table - server replied: Not Found

[taimoorzaeem]

It's hard to pinpoint the issue without the underlying PostgREST error message. To get that, please make the same request (preferably through curl or postman) directly to the running PostgREST instance without the reverse proxy in between.

Please also specify the PostgREST version you are using.

[vmgonzalez1990]

-> I use PostgREST 13.0.4

-> This is the output I get from curl. I've stopped the Nginx reverse proxy. It's as if it doesn't see the accept-profile header to determine the search scheme.

curl -X POST 'http://localhost:8000/dat_usuario'
-H "Content-Type: application/json"
-H "Prefer: return=minimal"
-H "Accept-Profile: mod_seguridad"
-d '{
"primernombre": "fname",
"segundonombre": "sname",
"primerapellido": "flname",
"segundoapellido": "slname",
"correo": "[email protected]",
"usuario": "user",
"contrasena": "pass",
"idrolusuario": 0,
"activado": false,
"autenticado": false
}'
{"code":"PGRST205","details":null,"hint":null,"message":"Could not find the table 'public.dat_usuario' in the schema cache"}

-> Same response with SoapUI

-> This is how my postgrest.conf is configured

Extra schemas to add to the search_path of every request

db-extra-search-path = "public,mod_nomenclador,mod_seguridad,mod_estructura,mod_consumo"

The name of which database schema to expose to REST clients

db-schemas = "public,mod_nomenclador,mod_seguridad,mod_estructura,mod_consumo"

[taimoorzaeem]

For POST method, you need to use Content-Profile header instead of Accept-Profile as mentioned in the docs.

[vmgonzalez1990]

Thank you very much @taimoorzaeem