Powerbox proxy reporting headersIncomplete

9 views
Skip to first unread message

Jay Gischer

unread,
Aug 9, 2024, 4:41:23 PM8/9/24
to Sandstorm Development
My proxy requests are not successful, despite putting up a powerbox and getting the access token correctly.  I pass it in the Authorization header correctly - as best I can tell from dumping the javascript (server side) objects.

The Sandstorm log shows Sandstorm throwing an error stating "headersIncomplete". 

The full text of the log entry is this:

kj/compat/http.c++:7233: info: threw exception while serving HTTP response; exception = (remote):0: failed: remote exception: expected headersComplete; HTTP response from sandboxed app had incomplete headers.

I have been looking through .../joyent-http/http-parser.c++  and it looks like this is due to the wrong pattern of <CR> and/or <LF> being sent from my library.  Is this correct?  Or is there a much more mundane reason for getting this error in the log?

Thanks,

-j

Troy Farrell

unread,
Aug 10, 2024, 8:19:42 AM8/10/24
to Sandstorm Development
Hi Jay,

Yes, I would check your app first.  The Joyent HTTP parser has been solid.  I've caused lots of Sandstorm error messages, but the HTTP parser has not been the source of any of mine.

Troy

Jay Gischer

unread,
Aug 16, 2024, 1:00:59 AM8/16/24
to Troy Farrell, Sandstorm Development
To be honest, I'm struggling.  Using the access token is not working, and I can't figure out why,.  I'm working in Meteor, thus Javascript/Node.  The error I get is a system error EAI_AGAIN from dnslookup.  This is documented as a dns timeout error.  However, this makes no sense.  I have printed out the host used for the call, and verified with copy and paste that it is valid, and my system is resolving it.  Meanwhile, it is my understanding that the bridge proxy should actually ignore this and use something else.

Having switched libraries, the log about "incomplete headers" has gone away, but the EAI_AGAIN remains, and my request doesn't work.   I have tried randomly changing things, to no avail.  My understanding/guess is that this error results from a refusal of the bridge proxy to forward my request.  I don't know why it is refusing, I have verified that my token is the one given to me and copied correctly.

I looked at the Wekan code, but if it uses the powerbox, I couldn't find it.

What's a good example of vanilla powerbox use?

On Tue, Aug 13, 2024 at 8:05 AM Jay Gischer <jgis...@gmail.com> wrote:
Thanks for your reply.

I figured the problem was with my app, or more specifically, a package I'm using.  It's more that I'm wondering what this message means about what is wrong.  I mean, is the package (Axios) actually sending headers in some incorrect way?

-j

--
You received this message because you are subscribed to the Google Groups "Sandstorm Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sandstorm-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sandstorm-dev/4e0cc4ad-1951-4555-a3dc-9fbadb55ff76n%40googlegroups.com.

Jay Gischer

unread,
Aug 16, 2024, 1:01:38 AM8/16/24
to Troy Farrell, Sandstorm Development
Thanks for your reply.

I figured the problem was with my app, or more specifically, a package I'm using.  It's more that I'm wondering what this message means about what is wrong.  I mean, is the package (Axios) actually sending headers in some incorrect way?

-j

On Sat, Aug 10, 2024 at 5:19 AM Troy Farrell <troyjf...@gmail.com> wrote:
--
Reply all
Reply to author
Forward
0 new messages