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

[DomCrawler] Dont use LIBXML_PARSEHUGE by default #17986

Merged
merged 1 commit into from Mar 2, 2016

Conversation

nicolas-grekas
Copy link
Member

Q A
Branch 2.3
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? no
Fixed tickets #16873, #17956
License MIT
Doc PR -

Because of http://symfony.com/blog/security-release-symfony-2-0-17-released

@fabpot
Copy link
Member

fabpot commented Mar 2, 2016

👍

@fabpot
Copy link
Member

fabpot commented Mar 2, 2016

Thank you @nicolas-grekas.

@fabpot fabpot merged commit fda32f8 into symfony:2.3 Mar 2, 2016
fabpot added a commit that referenced this pull request Mar 2, 2016
…-grekas)

This PR was merged into the 2.3 branch.

Discussion
----------

[DomCrawler] Dont use LIBXML_PARSEHUGE by default

| Q             | A
| ------------- | ---
| Branch        | 2.3
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | no
| Fixed tickets | #16873, #17956
| License       | MIT
| Doc PR        | -

Because of http://symfony.com/blog/security-release-symfony-2-0-17-released

Commits
-------

fda32f8 [DomCrawler] Dont use LIBXML_PARSEHUGE by default
@nicolas-grekas nicolas-grekas deleted the fix-huge branch March 2, 2016 15:26
@fabpot fabpot mentioned this pull request Mar 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants