-
Notifications
You must be signed in to change notification settings - Fork 61
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
HTTP::Headers Doesn't like SOAP::Lite fields named "APR::Table=HASH(0x7f7929552af0)" [rt.cpan.org #84461] #55
Comments
2013! |
Let's come to an agreement that if this is still open in 2021 we'll move it to yet another bug tracker. ;) Would you happen to know if this is still an issue? There was so much accumulated stuff in RT and we're very slowly trying to chip away at it. |
I have NFI. There have been a lot of changes to SOAP-Lite since April 2013, so maybe they worked around it or fixed it on their end? If not, I imagine if we do a new test of our SOAP server with updated RPMs I'll see it again. Dunno when or if that will happen. |
@redhotpenguin Have you noticed this in any of your testing? |
I use OCS Inventory, and followed a bug trail that led me here and I can confirm that there is still an issue in HTTP::Message 6.13 on Debian. I tried version 6.06 first, and then upgraded to 6.13. Error:
bug trail: |
The StackOverflow thread mentions installing 6.04 Are you able to test this with 6.05? I'd be interested to know if we can exactly pin down the version which introduces this problem. |
Ah, just re-read the original comment. It looks like this did break in 6.05 |
Would you still like me to try to test with 6.04 or 6.05? |
@mxroo I'm not sure we need to test that out now. The diff is here https://metacpan.org/diff/file?target=GAAS%2FHTTP-Message-6.05%2F&source=GAAS%2FHTTP-Message-6.04 |
Is this the culprit? 5aaa8144 |
Yup, sure looks like it to me. |
@mxroo Can you provide the actual XML it's trying to parse when the error occurs? (if it's a huge thing, cutting it down to the least amount of XML possible would be great.) Thanks! |
Here is the php script I was trying to run.
|
@redhotpenguin any thoughts as to how to proceed here? |
This is a bug in SOAP::Lite that apparently hasn't been noticed until HTTP::Message got strict enough to expose it. We (someone) should try to figure out where those headers are coming from and determine the actual intent. I would suggest looking at the full stack trace of the error that HTTP::Message gives, to find the place in SOAP::Lite that is creating the headers. |
Let me know if there is any other information I can provide to help on this issue. Thanks! |
@mxroo are you able to get at the underlying server code in order to get some debugging info? |
@oalders Probably, I have full root on all of my servers. What debugging information would help? |
|
@mxroo if you need any tips on getting at the XML and dumping it, we can help with that. |
Tips would be very helpful, thank you! |
@mxroo to get a better stack trace you could try adding a |
Since this is |
Does this help?
|
This seems to be a different error. Can you validate that the XML you're trying to send is correct? |
I'm not as fluent in XML, but it seems like the XML that that script is asking for is this:
from the bottom of this page: http://wiki.ocsinventory-ng.org/index.php?title=Developers:Web_services I got the exact same error in the apache logs when doing that. |
Is that the XML that is needed, or am I misunderstanding? I can try again. |
Migrated from rt.cpan.org#84461 (status was 'new')
Requestors:
Attachments:
From [email protected] on 2013-04-06 05:06:02:
The text was updated successfully, but these errors were encountered: