-
Notifications
You must be signed in to change notification settings - Fork 437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access-Control-Expose-Headers errors in browser when response from server #396
Comments
What does the response from the server look like in the browser? Could you show the output of the network tab in your browser debug tools? |
You shouldn't have to call |
What does the chrome console warning drop down say? I noticed you're serving the UI on HTTP but the grpcwebproxy on HTTPS, it's not a security mismatch? |
Pretty sure this is a CORS issue. Have you configured your proxy to enable
CORS preflight requests?
…On Mon, 22 Apr 2019, 22:29 scippio, ***@***.***> wrote:
I don't think so... but good point I'll try unify this...
[image: image]
<https://user-images.githubusercontent.com/672903/56532642-6fdf2a80-6556-11e9-9376-bcccac8e2539.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#396 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABQ36IZ3T4E2SXFPH7NZETPRYU5HANCNFSM4HHO2TYQ>
.
|
You can see the OPTIONS request and my server source for pre-flight setup... I don't using any proxy. Only this client and server code. |
Ok, I change my client code from "rpcCall" to "unaryCall" (promise version) (functions in generated js files from proto): So I change exactly this lines: // var client = new RegistrationServiceClient("https://localhost:8000")
var client = new RegistrationServicePromiseClient("https://localhost:8000")
// client.newRegistration(data,meta,(res) => {
// console.log("res:",res)
// })
client.newRegistration(data,meta).then((res) => {
console.log("res:",res)
console.log("res:",res.toObject())
}).catch((err) => {
console.log("err: ",err)
}) |
I think a found the same problem in the past: grpc/grpc-web#518 EDIT: So I think I will try use Envoy... |
Hi,
I'm playing with grpc-web and maybe I'm doing something wrong, but I'm geting this:
I'm sucessfully recieved request on server with all data... but response end with this errors in browser (Chrome) :(
My test code:
I create good request from my js client:
and on my golang server (in main func):
Verion grpc-web: 0.9.1
thanks for any help...
The text was updated successfully, but these errors were encountered: