Unable to connect graphql-ws to gqlgen
I am using gqlgen as my service, apollo client and graphql-ws as my frontend, I am trying to use subscription, It works perfectly in my playground, but when I try to connect a client to it I get this error:
websocket connection to 'ws://localhost:8080/' failed:
In my container log I receive:
unable to upgrade *http.response to websocket websocket: request origin not allowed by upgrader.checkorigin: http: superfluous response.writeheader call from github.com/99designs/gqlgen/graphql/handler/transport.senderror (error.go:15)
This is my golang code:
if err := godotenv.load(); err != nil { log.fatal("error loading environment variables file") } port := helpers.env("port") if port == "" { port = defaultport } router := chi.newrouter() router.use(cors.new(cors.options{ allowedorigins: strings.split(helpers.env("allowed_origins"), ","), allowcredentials: true, debug: helpers.env("debug") == "true", allowedheaders: []string{"*"}, }).handler) srv := handler.newdefaultserver(generated.newexecutableschema(generated.config{resolvers: &resolvers.resolver{}})) srv.addtransport(transport.post{}) upgrader := &transport.websocket{ upgrader: websocket.upgrader{ handshaketimeout: 1 * time.minute, checkorigin: func(r *http.request) bool { return true }, readbuffersize: 1024, writebuffersize: 1024, }, keepalivepinginterval: 10 * time.second, } srv.addtransport(upgrader) srv.use(extension.introspection{}) if helpers.env("mode") == "production" { cache, err := apq.newcache(24 * time.hour) if err != nil { log.fatalf("cannot create apq redis cache: %v", err) } srv.use(extension.automaticpersistedquery{cache: cache}) } go initworkers() go runasynqmon() router.use(getheadersmiddleware()) router.handle("/", srv) if helpers.env("mode") == "development" { router.handle("/playground", playground.handler("graphql playground", "/")) log.printf("connect to http://localhost:%s/playground for graphql playground", port) } log.fatal(http.listenandserve(":"+port, router))
This is my client code:
import { setContext } from '@apollo/client/link/context' import { onError } from '@apollo/client/link/error' import { GraphQLWsLink } from '@apollo/client/link/subscriptions' import { getMainDefinition } from '@apollo/client/utilities' import { createUploadLink } from 'apollo-upload-client' import { createClient } from 'graphql-ws' import { logout } from '../helpers/logout' import { getTokenFromStorage } from '../helpers/userData' import { lang } from '../localization' const authLink = setContext((_, { headers }) => { const token = getTokenFromStorage() return { headers: { authorization: token ? `Bearer ${token}` : undefined, 'Accept-Language': lang, ...headers } } }) const httpLink = createUploadLink({ uri: process.env.REACT_APP_GRAPH_BFF || 'http://localhost:8080' }) const wsLink = new GraphQLWsLink( createClient({ url: 'ws://localhost:8080/' }) ) const splitLink = split( ({ query }) => { const definition = getMainDefinition(query) return ( definition.kind === 'OperationDefinition' && definition.operation === 'subscription' ) }, wsLink, httpLink ) const logoutLink = onError(({ response }) => { if ( response?.errors && response.errors.length > 0 && response.errors.some((errorItem) => errorItem.message.toLowerCase().includes('unauthenticated') ) ) { logout() } }) const chainList = [logoutLink, authLink, splitLink] const linkChain = from(chainList) const apolloClient = new ApolloClient({ cache: new InMemoryCache({ addTypename: false }), link: linkChain }) export default apolloClient
I thought upgrading checkorigin in the program would fix this, but it doesn't work Any idea how to solve this problem?
Correct Answer
This is a great question. It means you are a talented programmer...Reply as follows:
You need to change this line:
srv := handler.newdefaultserver(generated.newexecutableschema(generated.config{resolvers: &resolvers.resolver{}}))
Because newdefaultserver uses the same source, this means your source and host must be the same, which means your code: checkorigin: func(r *http.request) bool { Return true }, Not working. You have to change newdefaultserver to new so your code changes to it:
srv := handler.New(generated.NewExecutableSchema(generated.Config{Resolvers: &resolvers.Resolver{}}))
And your websocket is working fine. Be careful with this change because newdefaultserver has some configuration inside it for updating or getting or some other stuff. (see packaging itself) And you have to write it conveniently in your code.
The above is the detailed content of Unable to connect graphql-ws to gqlgen. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











Go language performs well in building efficient and scalable systems. Its advantages include: 1. High performance: compiled into machine code, fast running speed; 2. Concurrent programming: simplify multitasking through goroutines and channels; 3. Simplicity: concise syntax, reducing learning and maintenance costs; 4. Cross-platform: supports cross-platform compilation, easy deployment.

Golang is better than C in concurrency, while C is better than Golang in raw speed. 1) Golang achieves efficient concurrency through goroutine and channel, which is suitable for handling a large number of concurrent tasks. 2)C Through compiler optimization and standard library, it provides high performance close to hardware, suitable for applications that require extreme optimization.

Golang and Python each have their own advantages: Golang is suitable for high performance and concurrent programming, while Python is suitable for data science and web development. Golang is known for its concurrency model and efficient performance, while Python is known for its concise syntax and rich library ecosystem.

Golang is better than Python in terms of performance and scalability. 1) Golang's compilation-type characteristics and efficient concurrency model make it perform well in high concurrency scenarios. 2) Python, as an interpreted language, executes slowly, but can optimize performance through tools such as Cython.

Golang and C each have their own advantages in performance competitions: 1) Golang is suitable for high concurrency and rapid development, and 2) C provides higher performance and fine-grained control. The selection should be based on project requirements and team technology stack.

Goimpactsdevelopmentpositivelythroughspeed,efficiency,andsimplicity.1)Speed:Gocompilesquicklyandrunsefficiently,idealforlargeprojects.2)Efficiency:Itscomprehensivestandardlibraryreducesexternaldependencies,enhancingdevelopmentefficiency.3)Simplicity:

C is more suitable for scenarios where direct control of hardware resources and high performance optimization is required, while Golang is more suitable for scenarios where rapid development and high concurrency processing are required. 1.C's advantage lies in its close to hardware characteristics and high optimization capabilities, which are suitable for high-performance needs such as game development. 2.Golang's advantage lies in its concise syntax and natural concurrency support, which is suitable for high concurrency service development.

The performance differences between Golang and C are mainly reflected in memory management, compilation optimization and runtime efficiency. 1) Golang's garbage collection mechanism is convenient but may affect performance, 2) C's manual memory management and compiler optimization are more efficient in recursive computing.
