Hi Attila, I've started to use Teapot for a backend and it feels really great. Thanks

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

Oh missed that we can do that. Closing it. Thank you <a class="user-mention notranslat

Default exception handler can't be set with custom headers about teapot HOT 2 CLOSED

zeroflag commented on July 17, 2024

Default exception handler can't be set with custom headers

from teapot.

Comments (2)

zeroflag commented on July 17, 2024 1

Hi @sebastianconcept, thanks for reporting this.

Just to be sure I'm understand the problem properly, is the main goal to set the response headers on an aborted response?

If yes, then I think this way it should work:

Teapot stopAll.

Teapot on
  GET: '/' -> [:req | 
    req abort:
      (TeaResponse unauthorized   
        headers: { 'test-header' -> 'test-value' } asDictionary;
        yourself).
];
start.

$ curl -v http://localhost:1701/
*   Trying ::1...
* TCP_NODELAY set
* Connection failed
* connect to ::1 port 1701 failed: Connection refused
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 1701 (#0)
> GET / HTTP/1.1
> Host: localhost:1701
> User-Agent: curl/7.64.1
> Accept: */*
> 
< HTTP/1.1 401 Unauthorized
< Server: Zinc HTTP Components 1.0 (Pharo/10.0)
< Date: Sun, 29 Jan 2023 20:35:34 GMT
< test-header: test-value
< Content-Type: text/html;charset=utf-8
< Content-Length: 2
<