Skip to content

issue with verifyProxy #118

Answered by kinngh
john-kuo asked this question in Q&A
Feb 26, 2024 · 1 comments · 3 replies
Discussion options

You must be logged in to vote
  • If you want to test it with Postman, what I usually do is update my verifyRequest to
const isDev = process.env.NODE_ENV === "dev";
if (isDev) {
 // pass a new header entry that says `postman` or something similar
 // assign a dev store session token
 // next()
}

This ensures that only in dev mode, you can use a custom header to bypass the entire check, assign a dev store and move on with your request.

  • The ngrok issue - I usually don't run into this for some reason on my ngrok account but everyone else does, including me if I make a new ngrok account. There's 3 things here:
  1. In your browser, like the page instructs, use a custom User-Agent. I like to name mine after my first name and t…

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@john-kuo
Comment options

@kinngh
Comment options

Answer selected by john-kuo
@john-kuo
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
user error Issue in configuration from the user's end, mostly because of human error or bad docs
2 participants