Question: Need support for chrome?

[josejuanmontiel]

I use from firefox without problem.. but when test in chrome i receive this kind of subscrition: {"endpoint":"https://fcm.googleapis.com/fcm/send/eYLp09S5j84:APA91bGOu3LR0Hma.... and when used to send the notificacion this message: A valid push subscription endpoint should be specified in the URL as such: https://fcm.googleapis.com/wp/dHIoDxE7Hdg:APA91bH1Zj0kNa...

Probably need implement this https://firebase.google.com/docs/cloud-messaging/migrate-v1?

Thanks.

[josejuanmontiel]

Something like this could help to override the header like explained here https://developer.chrome.com/blog/web-push-interop-wins#introducing_vapid_for_server_identification

// CustomTransport agrega headers personalizados
type CustomTransport struct {
	Base    http.RoundTripper
	Headers map[string]string
}

func (t *CustomTransport) RoundTrip(req *http.Request) (*http.Response, error) {
	reqCopy := req.Clone(req.Context())

	vapidHeader := req.Header.Get("Authorization")
	if vapidHeader != "" {
		parts := strings.Split(vapidHeader, ",")
		if len(parts) == 2 {
			jwtPart := strings.TrimPrefix(parts[0], "vapid t=")
			t.Headers["Authorization"] = "WebPush " + jwtPart
		}
	}

	for k, v := range t.Headers {
		reqCopy.Header.Set(k, v)
	}

	return t.Base.RoundTrip(reqCopy)
}

func main() {

	// Decode subscription
	s := &webpush.Subscription{}
	json.Unmarshal([]byte(subscription), s)

	headers := map[string]string{
		"Crypto-Key": "p256ecdsa=" + vapidPublicKey,
	}

	client := &http.Client{
		Transport: &CustomTransport{
			Base:    http.DefaultTransport,
			Headers: headers,
		},
	}

	// Send Notification
	resp, err := webpush.SendNotification([]byte("Test"), s, &webpush.Options{
		HTTPClient:      client,
		Subscriber:      "example@example.com", // Do not include "mailto:"
		VAPIDPublicKey:  vapidPublicKey,
		VAPIDPrivateKey: vapidPrivateKey,
		TTL:             30,
	})
        ....

[joeblew999]

Nice one Josh .

Seems Google changed the way it works.

Need to test this :)

I am use cloud flare works with golang

[mawngo]

The changes you mentioned only affect Firebase and do not affect Chrome web push API.

The reason for that response could be due to Google removing inactive subscription

I have no problems sending hundred million notifications daily.