Dimitris | Clerk
Dimitris | Clerk
PostsComments
RRailway
Created by Dimitris | Clerk on 6/1/2023 in #✋｜help
Add up.railway.app to PSL
At Clerk, we have some validation on application domains (i believe that are other auth providers that may have those checks) based on the PSL that fail when using the generated domains from the Railway App dashboard. Is it possible to submit the eTLD+1 up.railway.app to the PSL ? More information and reasons to submit the up.railway.app to PSL can be found here: https://publicsuffix.org/learn/ Submit amendments docs: https://publicsuffix.org/submit/ Railway App Project ID: dca25c2a-c0e2-4cf2-9d5c-3938efc1def4
12 replies
RRailway
Created by Dimitris | Clerk on 5/31/2023 in #✋｜help
Invalid X-Forwarded-Port for NextJS deployed application
I have created a NextJS application aws-clerk-nextjs-production.up.railway.app. Logging the x-forwarded-port in the console it seems that instead of either a 443,80 or a 443 value we probably get the value of latest node from the route path. 
{
origin: null,
host: 'aws-clerk-nextjs-production.up.railway.app',
forwardedPort: '80',
forwardedHost: 'aws-clerk-nextjs-production.up.railway.app',
forwardedProto: 'https,http',
referrer: null,
userAgent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36'
}
{
origin: null,
host: 'aws-clerk-nextjs-production.up.railway.app',
forwardedPort: '80',
forwardedHost: 'aws-clerk-nextjs-production.up.railway.app',
forwardedProto: 'https,http',
referrer: null,
userAgent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36'
}
The same application deployed in a AWS Amplify Hosting we get both forwardedPort: '443,80', so i guest it's related to how the headers between nodes of the network are propagated and how it's being merged. Is there a more official way to file a bug report? Do you need more details? Is there a guide i should take a look and improve this report?
13 replies