Description:
------------
Stream path can contain any character, whether URL encoded or not, except for the null character. Including a null character in the path raises the following error:

file_get_contents() expects parameter 1 to be a valid path, string given

Both the use case and test suite to support the claims above can be found at https://github.com/Bilge/VerbatimStream/tree/eb185806f9bea3ee65b7d0f3e42dcd27a7b40614

The use case is a custom stream wrapper that takes the path and converts it into a read-only data stream. The current workaround is to urlencode any path that contains nulls. However, this approach provides little benefit over the data wrapper. Being able to include nulls directly in the path would eliminate unnecessary url encoding and decoding in the custom wrapper implementation.


Test script:
---------------
file_get_contents("\000");

//or

file_get_contents("verbatim://\000");

Expected result:
----------------
No error.

Actual result:
--------------
file_get_contents() expects parameter 1 to be a valid path, string given