-
Notifications
You must be signed in to change notification settings - Fork 625
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
Adding extra header values to HTTP request #1047
Comments
Hello Phil! How about the With best regards, Elmer |
Hi Elmer, Thanks for the reply - we've been using the I couldn't see how either Best wishes, Phil |
Hello @FatherFil, When you use |
Hi @thinkingserious , When I tried using those functions, yes, I could see the headers in the email header, however the issue is not with the email headers, but the HTTP request headers. The SendGrid security team are asking me to add extra values to the HTTP request header in order to prove the request is genuine and allow me to bypass some of their restrictions. I believe the |
Thanks for the elaboration @FatherFil, I think adding a helper to pass in additional headers to the |
@thinkingserious Thank you. And for the example of setting the request headers. |
The emails we send using SendGrid usually contain a lot of bona-fide links and this has occasionally tripped the security filters at SendGrid, resulting in our emails not being sent. Once we confirmed with SendGrid Security Team that our links are okay and not spam we were asked to include a special key in the header of our API requests.
After much to and fro between our dev team and the SendGrid support team, on how best to do this, and exactly why it would be bad practice to fork the official repo and mangle the code to add the key in manually, I wondered whether it was possible to add in the ability to push a new header key value pair into the base HTTP request in
sendgrid\lib\BaseSendGridClientInterface.php
I'm happy to craft something and submit a pull request but I wanted to check first that:
Many thanks,
Phil
The text was updated successfully, but these errors were encountered: