#Problem Processing Request w/ graphql subscription on public api
34 messages · Page 1 of 1 (latest)
5601a4f4-da8e-4978-9e2f-ac476d3cb851
i must ask, what is the usecase, im intrigued
making my own railway client!
do tell more
ok ok I will spoil the fun - I was looking through the careers page and you all mention the async project, where candidates build an app to spin containers up and down. I thought it sounded neat and wanted to build this myself. I want to add a few bells and whistles, so I thought I'd take a stab at graphql subscriptions.
also, I understand you probably have more pressing things to focus on so don't worry about the above if you don't have time. I just thought it was odd and could possibly be a bug so I wanted to reach out
nvm, got it 🙂
😦 and i was preparing code for you
hey @limber dragon what do ya' think?
thats very nice, well done! now let me publicly view your logs 
hehehe
cool project btw
did u have any graphql knowledge prior to this?
the reverse proxy is very interesting
I might do something similar
wdym? in his project?
their site calls a reverse proxy that adds auth to the gql requests
and avoids cors
yea I'm not interacting with the public API on the client, yet on my backend
I'm using my account token for auth and I didn't want to leak that on the client 🙂
yep, though nothing crazy
hmmm
so could i make any request to the proxy and have it auth it for me?
yes 🫣 - I thought about adding another layer of auth between the client and server but didn't for the sake of time. the project requirements dictated a frontend and backend, and more-so made the backend to meet requirements
anyways I emailed Ian so hopefully I hear back 
good luck! 