Bug #52404 [Com]: All TTF Files are invalid [ALL PHP.NET]
Edit report at https://bugs.php.net/bug.php?id=52404&edit=1 ID: 52404 Comment by: clockw...@php.net Reported by:h...@php.net Summary:All TTF Files are invalid [ALL PHP.NET] Status: Open Type: Bug Package:*General Issues PHP Version:Irrelevant Block user comment: N Private report: N New Comment: This... doesn't seem to be just those .ttf files. I grabbed http://ftp.gnome.org/pub/GNOME/sources/ttf-bitstream-vera/1.10/ and there's no differences against http://github.com/pear/Image_Text/tests/ Trying to open these; I get: imagettfbbox(): Could not read font Previous Comments: [2011-06-12 03:32:01] gozmeu at gmail dot com same here Warning: imagettftext() [function.imagettftext]: Could not find/open font in /home/gozmeu/domains/pwiguilds.com/public_html/travelcounter.php on line 40 â°PNG IHDRP Ã-q" PLTEÿÿÿÿÿÿsxÂ¥c IDAT(âcpñ,»ÃQ3GÃÃk&]7> 7¡ËFIEND®B`â with a valid or invalid ttf file :s [2010-12-07 12:51:33] h...@php.net This is not a difficult bug to fix. Anybody with commit access should be able to fix it. Can somebody fix it? Thanks. [2010-10-18 18:30:24] h...@php.net I would if I could. I don't think I have commit access to all of the ttf files on the php.net svn. [2010-07-27 01:54:48] ras...@php.net You may just have to re-import them into Subversion or something. All I did was flip the svn property so Subversion wouldn't mangle them. [2010-07-27 01:02:53] ka...@php.net Confirmed on Windows XP aswell (unreadable font files in the font viewer) Rasmus: You did this change, should it be reverted or do you have any easy fix on your mind? The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=52404 -- Edit this bug report at https://bugs.php.net/bug.php?id=52404&edit=1
Bug #47761 [Com]: Since 5.2.9 SoapClient no longer attempts Basic auth to retrieve a WSDL file
Edit report at https://bugs.php.net/bug.php?id=47761&edit=1 ID: 47761 Comment by: clockw...@php.net Reported by:marques at displague dot com Summary:Since 5.2.9 SoapClient no longer attempts Basic auth to retrieve a WSDL file Status: No Feedback Type: Bug Package:SOAP related Operating System: * PHP Version:5.2.9 Block user comment: N Private report: N New Comment: $ php -v PHP 5.2.17-0.dotdeb.0 with Suhosin-Patch 0.9.7 (cli) (built: Jan 7 2011 07:47:48) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.2.0, Copyright (c) 1998-2010 Zend Technologies Doing: '...', 'password' => '...', 'trace' => 1, 'exceptions' => true, ); $code_table_client = new RPDesktopCodeTableSoapClient(new SoapClient($wsdl, $soapOptions)); The basic auth works for the initial connection, but other components of the WSDL that are being referred to don't load the credentials. Previous Comments: [2009-10-07 01:00:00] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". [2009-09-29 11:20:40] sjo...@php.net Thank you for your bug report. How did you try to pass the username and password to the SOAP client? Please try putting them in the URL, like this: http://user:p...@www.example.com/service.wsdl [2009-08-07 03:52:10] marques at displague dot com One scenario, you are making your own SOAP Server service. It is more difficult to write a digest auth server than it is to write a basic auth server. Again, consider that PHP web requests are all made as HTTP/1.0 because Chunk decoding is not handled properly (or at all) and so Digest, which is HTTP/1.1 specific is technically not an option without a good deal of custom coding. Aside from that, I imagine there are just some HTTP/1.0 or Basic only servers out there. [2009-08-06 22:02:12] sriram dot natarajan at gmail dot com why is there still a need to support basic authentication ? can u kindly explain that scenario ? [2009-03-24 13:53:48] marques at displague dot com Description: Since 5.2.9, SoapClient no longer attempts HTTP Basic authentication to retrieve a wsdl file. Prior to this version Basic was attempted and Digest was not. Digest should also be attempted but that is a matter for another bug. The SoapClient option 'authentication' has no effect on wsdl retrieval. A work-around is to fetch the WSDL file manually or via PHP commands within the SOAP code, but that method can be cumbersome because digest auth code has to be written from scratch and Bug #47759 (chunk encoding) can get in the way. -- Edit this bug report at https://bugs.php.net/bug.php?id=47761&edit=1
Bug #47761 [Com]: Since 5.2.9 SoapClient no longer attempts Basic auth to retrieve a WSDL file
Edit report at https://bugs.php.net/bug.php?id=47761&edit=1
ID: 47761
Comment by: clockw...@php.net
Reported by:marques at displague dot com
Summary:Since 5.2.9 SoapClient no longer attempts Basic auth
to retrieve a WSDL file
Status: No Feedback
Type: Bug
Package:SOAP related
Operating System: *
PHP Version:5.2.9
Block user comment: N
Private report: N
New Comment:
See https://gist.github.com/1765797
The WSDL depicted there is behind a load balancer which deals with the SSL bits
- it's actually served
over https.
While the initial basic auth works, further requests don't appear to.
I suspect>
1. WSDL loaded over HTTPS with HTTP Basic Auth
2. WSDL points to a http address with a port, which is not recognised as the
same site
3. A new request is made to grab the xsd bits
4. The server redirects http to https
Expected:
At step 4, the http basic auth credentials are used
Actual:
SoapFault exception: [WSDL] SOAP-ERROR: Parsing Schema: can't import schema
from
'http://*:80/codetable-service/CodeTableService?xsd=3' in settings.php:82
Stack trace:
#0 settings.php(82): SoapClient->SoapClient('https://...', Array)
#1 ettings.php(2): require('...')
#2 {main}
Warning:
SoapClient::SoapClient(http://:80/codetable-service/CodeTableService?xsd=3)
[soapclient.soapclient]: failed to open stream: HTTP request failed! HTTP/1.1
401 Unauthorized in
settings.php on line 82
Warning: SoapClient::SoapClient() [soapclient.soapclient]: I/O warning : failed
to load external entity
"http://:80/codetable-service/CodeTableService?xsd=3"; in settings.php on
line 82
Previous Comments:
--------
[2012-02-08 05:31:24] clockw...@php.net
$ php -v
PHP 5.2.17-0.dotdeb.0 with Suhosin-Patch 0.9.7 (cli) (built: Jan 7 2011
07:47:48)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2010 Zend Technologies
Doing:
'...',
'password' => '...',
'trace' => 1,
'exceptions' => true,
);
$code_table_client = new RPDesktopCodeTableSoapClient(new SoapClient($wsdl,
$soapOptions));
The basic auth works for the initial connection, but other components of the
WSDL that are being referred to don't load the credentials.
[2009-10-07 01:00:00] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[2009-09-29 11:20:40] sjo...@php.net
Thank you for your bug report.
How did you try to pass the username and password to the SOAP client? Please
try putting them in the URL, like this:
http://user:p...@www.example.com/service.wsdl
[2009-08-07 03:52:10] marques at displague dot com
One scenario, you are making your own SOAP Server service. It is more
difficult to write a digest auth server than it is to write a basic auth
server. Again, consider that PHP web requests are all made as HTTP/1.0 because
Chunk decoding is not handled properly (or at all) and so Digest, which is
HTTP/1.1 specific is technically not an option without a good deal of custom
coding.
Aside from that, I imagine there are just some HTTP/1.0 or Basic only servers
out there.
[2009-08-06 22:02:12] sriram dot natarajan at gmail dot com
why is there still a need to support basic authentication ? can u kindly
explain that scenario ?
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=47761
--
Edit this bug report at https://bugs.php.net/bug.php?id=47761&edit=1
Bug #47761 [Com]: Since 5.2.9 SoapClient no longer attempts Basic auth to retrieve a WSDL file
Edit report at https://bugs.php.net/bug.php?id=47761&edit=1
ID: 47761
Comment by: clockw...@php.net
Reported by:marques at displague dot com
Summary:Since 5.2.9 SoapClient no longer attempts Basic auth
to retrieve a WSDL file
Status: No Feedback
Type: Bug
Package:SOAP related
Operating System: *
PHP Version:5.2.9
Block user comment: N
Private report: N
New Comment:
Further exploration of this issue, after ensuring everything is running happily
on https:
Configuring a URI of https://name/path/to/wsdl
and receiving a WSDL with
https://name:443/path/to/WSDL/bit
... fails to trigger the authentication.
Evidently, "https://name:443"; and "https://name"; are considered different URIs,
even if they are equivalent.
Previous Comments:
----
[2012-02-08 05:38:38] clockw...@php.net
See https://gist.github.com/1765797
The WSDL depicted there is behind a load balancer which deals with the SSL bits
- it's actually served
over https.
While the initial basic auth works, further requests don't appear to.
I suspect>
1. WSDL loaded over HTTPS with HTTP Basic Auth
2. WSDL points to a http address with a port, which is not recognised as the
same site
3. A new request is made to grab the xsd bits
4. The server redirects http to https
Expected:
At step 4, the http basic auth credentials are used
Actual:
SoapFault exception: [WSDL] SOAP-ERROR: Parsing Schema: can't import schema
from
'http://*:80/codetable-service/CodeTableService?xsd=3' in settings.php:82
Stack trace:
#0 settings.php(82): SoapClient->SoapClient('https://...', Array)
#1 ettings.php(2): require('...')
#2 {main}
Warning:
SoapClient::SoapClient(http://:80/codetable-service/CodeTableService?xsd=3)
[soapclient.soapclient]: failed to open stream: HTTP request failed! HTTP/1.1
401 Unauthorized in
settings.php on line 82
Warning: SoapClient::SoapClient() [soapclient.soapclient]: I/O warning : failed
to load external entity
"http://:80/codetable-service/CodeTableService?xsd=3"; in settings.php on
line 82
--------
[2012-02-08 05:31:24] clockw...@php.net
$ php -v
PHP 5.2.17-0.dotdeb.0 with Suhosin-Patch 0.9.7 (cli) (built: Jan 7 2011
07:47:48)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2010 Zend Technologies
Doing:
'...',
'password' => '...',
'trace' => 1,
'exceptions' => true,
);
$code_table_client = new RPDesktopCodeTableSoapClient(new SoapClient($wsdl,
$soapOptions));
The basic auth works for the initial connection, but other components of the
WSDL that are being referred to don't load the credentials.
[2009-10-07 01:00:00] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[2009-09-29 11:20:40] sjo...@php.net
Thank you for your bug report.
How did you try to pass the username and password to the SOAP client? Please
try putting them in the URL, like this:
http://user:p...@www.example.com/service.wsdl
[2009-08-07 03:52:10] marques at displague dot com
One scenario, you are making your own SOAP Server service. It is more
difficult to write a digest auth server than it is to write a basic auth
server. Again, consider that PHP web requests are all made as HTTP/1.0 because
Chunk decoding is not handled properly (or at all) and so Digest, which is
HTTP/1.1 specific is technically not an option without a good deal of custom
coding.
Aside from that, I imagine there are just some HTTP/1.0 or Basic only servers
out there.
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=47761
--
Edit this bug report at https://bugs.php.net/bug.php?id=47761&edit=1
Bug #46792 [Com]: SoapFault detail property missing
Edit report at http://bugs.php.net/bug.php?id=46792&edit=1
ID: 46792
Comment by: clockw...@php.net
Reported by:daniel dot oconnor at gmail dot com
Summary:SoapFault detail property missing
Status: Bogus
Type: Bug
Package:SOAP related
Operating System: Windows
PHP Version:5.2.7
Assigned To:dmitry
Block user comment: N
New Comment:
Another variant:
PHP 5.2.13, somehow someone is raising soapfaults without a faultcode
(or it's null, or something); which is being raised by the soapclient
object.
try {
$sc = new SoapClient(...);
$sc->foo();
} catch (SoapFault $sf) {
var_dump($sf->faultcode); // E_NOTICE!
}
This results in:
Undefined property: SoapFault::$faultcode in
/var/www/vx/include/classes/queue/OrderAction.php on line 19
when you try and check it.
Given that the constructor requires you to provide a faultcode
(http://au.php.net/soapfault); if the soapfault object doesn't set
default properties, at least ensure where it's invoked by the soapclient
passes in the right parameters.
It's the same scenario as the original report; just a different
property.
Previous Comments:
[2009-04-25 17:42:56] daniel dot oconnor at gmail dot com
I still feel it should be defined all of the time, and just set to null
if there's nothing there; like every other object in PHP.
As a normal developer, I shouldn't have to remember that if I want to
check my soapfault detail I have to wrap it in isset(), because this is
one of the few niche bits of PHP which break convention.
This bug exposes two seperate problems - class definition and how that
object is rendered.
My problem is with the class definition/instatiation not fitting with
how every other class I know of behaves.
For your problems, with rendering/encoding soapfault detail needlessly,
why not just check if the property is null or not in the encoding step?
And if its that big of a concern, what about spinning of another ticket
to specifically deal with that?
[2009-04-25 16:20:10] j...@php.net
As Dmitry said. Use isset().
[2009-01-11 10:56:45] daniel dot oconnor at gmail dot com
Not having the property defined was surprising, and unexpected - I would
not expect code which reads SoapFault::$detail to ever generate an
E_NOTICE.
[2009-01-11 09:40:03] dmi...@php.net
I don't think we should create empty "detail" property (and then encode
it and send back to client) if it's not important. Very rare script
looks into fault details. In case your script really needs it, it can
always check it with isset() or empty().
[2008-12-31 17:39:13] fel...@php.net
Hi Dmitry, any objection?
http://felipe.ath.cx/diff/bug46792.diff
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/bug.php?id=46792
--
Edit this bug report at http://bugs.php.net/bug.php?id=46792&edit=1
