Skip to content
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

[5.2] Set connection timeout for mail transports #13621

Merged
merged 6 commits into from
May 22, 2016
Merged

[5.2] Set connection timeout for mail transports #13621

merged 6 commits into from
May 22, 2016

Conversation

RTLer
Copy link
Contributor

@RTLer RTLer commented May 19, 2016

Hi,
By sending this PR I want to set connection timeout for drivers that use GuzzleHttp to send request
GuzzleHttp Use 0 to wait indefinitely (the default behavior) for connection timeout and that's really bad for background jobs like queue
it could cause infinite loops.

Regards,

@it-can
Copy link
Contributor

it-can commented May 19, 2016

Maybe make it a config option?

@GrahamCampbell GrahamCampbell changed the title Set connection timeout for mail transports [5.2] Set connection timeout for mail transports May 19, 2016
RTLer added 2 commits May 19, 2016 14:47
 and add default config for it on HttpClient in TransportManager
@RTLer
Copy link
Contributor Author

RTLer commented May 19, 2016

i see it now, in TransportManager they made pussible set guzzle config for driver's that work with guzzle,

'sparkpost' => [
    'secret' => 'c0100484e20bfa12e20632b1d9b4761a51c482c2',
    'guzzle' => [
        'connect_timeout' =>60,
    ],
]

i added the getHttpClient to create http client
and set config's and set default config for connect_timeout
in TransportManager
a7091fd

i push die setting by mistake, sorry
@taylorotwell taylorotwell merged commit 4fdd0d2 into laravel:5.2 May 22, 2016
@taylorotwell
Copy link
Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants