Skip to content
Written with Claude
IMPORTANT

As you may notice, this page and pretty much the entire website were obviously created with the help of AI. I wonder how you could tell? Was it a big "Written With Claude" badge on every page? I moved it to the top now (with the help of AI of course) to make it even more obvious. There are a few blogposts that were written by me manually, the old-fashioned way, I hope there will be more in the future, and those have a similar "Human Written" badge. This project (not the website), on the other hand, is a very, very different story. It took me more than two years of painstaking and unpaid work in my own free time. A story that, hopefully, I will tell someday. But meanwhile, what would you like me to do? To create a complex documentation website with a bunch of highly technical articles with the help of AI and fake it, to give you an illusion that I also did that manually? Like the half of itnernet is doing at this point? How does that makes any sense? Is that even fair to you? Or maybe to create this website manually, the old-fashioned way, just for you? While working a paid job for a salary, most of you wouldn't even get up in the morning. Would you like me to sing you a song while we're at it? For your personal entertainment? Seriously, get a grip. Do you find this information less valuable because of the way this website was created? I give my best to fix it to keep the information as accurate as possible, and I think it is very accurate at this point. If you find some mistakes, inaccurancies or problems, there is a comment section at the bottom of every page, which I also made with the help of the AI. And I woould very much appreciate if you leave your feedback there. Look, I'm just a guy who likes SQL, that's all. If you don't approve of how this website was constructed and the use of AI tools, I suggest closing this page and never wever coming back. And good riddance. And I would ban your access if I could know how. Thank you for your attention to this matter.

Response Headers

Set custom HTTP response headers for the endpoint.

Syntax

<Header-Name>: <value>

Response headers use standard HTTP header format with a colon separator. Header names are case-insensitive.

Examples

Set Content-Type

sql
create function get_html_page()
returns text
language sql
as $$select '<html><body><h1>Hello</h1></body></html>'$$;

comment on function get_html_page() is
'HTTP GET
Content-Type: text/html';

Response includes: Content-Type: text/html

Multiple Headers

sql
create function get_api_data()
returns json
language sql
as $$select '{"status": "ok"}'::json$$;

comment on function get_api_data() is
'HTTP GET
Content-Type: application/json
Cache-Control: no-store
X-Custom-Header: custom-value';

Response includes all three headers.

Multi-Value Headers

Headers with the same name are combined:

sql
create function set_cookies()
returns text
language sql
as $$select 'OK'$$;

comment on function set_cookies() is
'HTTP GET
Set-Cookie: session=abc123
Set-Cookie: theme=dark
Set-Cookie: lang=en';

Response includes: Set-Cookie: session=abc123, theme=dark, lang=en

Cache Control

sql
create function get_static_config()
returns json
language sql
as $$select config from app_config where id = 1$$;

comment on function get_static_config() is
'HTTP GET
Cache-Control: public, max-age=3600';

Clients can cache the response for 1 hour.

Combined with Other Annotations

sql
create function export_report()
returns text
language sql
as $$...$$;

comment on function export_report() is
'HTTP GET
@authorize manager
Content-Type: text/csv
Content-Disposition: attachment; filename="report.csv"
Cache-Control: no-cache';

Dynamic Headers from Parameters

Header values can include parameter values using the {param_name} template syntax:

sql
create function export_report(_type text, _file text)
returns text
language sql
as $$...$$;

comment on function export_report(text, text) is
'HTTP GET
@authorize manager
Content-Type: {_type}
Content-Disposition: attachment; filename={_file}
Cache-Control: no-cache';

Request: GET /api/export-report?_type=text/csv&_file=report.csv

Response headers:

Content-Type: text/csv
Content-Disposition: attachment; filename=report.csv

CORS Headers

sql
create function cors_endpoint()
returns json
language sql
as $$select '{}'::json$$;

comment on function cors_endpoint() is
'HTTP GET
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST
Access-Control-Allow-Headers: Content-Type';

Note: For comprehensive CORS support, use the CORS configuration instead.

Common Headers

HeaderPurpose
Content-TypeResponse media type
Cache-ControlCaching directives
Content-DispositionDownload filename
X-*Custom application headers
Set-CookieSet cookies
  • RAW - Return raw text output
  • CACHED - Server-side caching

Comments

Released under the MIT License.