Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #17655
| From | "Christoph M. Becker" <cmbecker69@arcor.de> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: incorrect PHP code |
| Date | 2018-01-18 17:18 +0100 |
| Organization | solani.org |
| Message-ID | <p3qhdd$mb0$1@solani.org> (permalink) |
| References | <e3016dthjg2scalgsutum253478r4t1dsh@4ax.com> <p3qarg$hfm$1@solani.org> <glg16dtr9pkfg0hjtttepj7aiiqlg4engm@4ax.com> |
On 18.01.2018 at 16:57, nospam@ms.com wrote: > On Thu, 18 Jan 2018 15:26:58 +0100, "Christoph M. Becker" > <cmbecker69@arcor.de> wrote: > >> On 18.01.2018 at 12:12, nospam@ms.com wrote: >> >>> The following PHP code does not work correctly; >> >> What do you expect the code to do, and what does it do? See also >> <http://www.catb.org/esr/faqs/smart-questions.html>. > > It's for a CAPTCHA verification. It's hosted with GoDaddy. On the old > server, it worked. It's been transferred to a new server, and it > doesn't work. > > The PHP spits out the following HTML code; > > <img > src="scripts/captcha/index.php?PHPSESSID=331f5041b67145685c5401104c602876" > style="vertical-align:middle" /> That's basically fine. > So for some reason the IMG element fails to load the image. I'd paste the URL of the image into the browser's address line, and check the response; particularly the status code, and in case of 200, I'd check the response body, if necessary with a hex viewer. By the way, php.general isn't a newsgroup, as far as I know. Did you mean the php-general@lists.php.net mailing list? -- Christoph M. Becker
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
incorrect PHP code nospam@ms.com - 2018-01-18 11:12 +0000
Re: incorrect PHP code Ifrit <ifrit@jahannam> - 2018-01-18 12:57 +0100
Re: incorrect PHP code nospam@ms.com - 2018-01-18 12:02 +0000
Re: incorrect PHP code Ifrit <ifrit@jahannam> - 2018-01-18 14:36 +0100
Re: incorrect PHP code Ifrit <ifrit@jahannam> - 2018-01-18 14:39 +0100
Re: incorrect PHP code Ifrit <ifrit@jahannam> - 2018-01-18 16:33 +0100
Re: incorrect PHP code nospam@ms.com - 2018-01-18 15:51 +0000
Re: incorrect PHP code "Christoph M. Becker" <cmbecker69@arcor.de> - 2018-01-18 15:26 +0100
Re: incorrect PHP code nospam@ms.com - 2018-01-18 15:57 +0000
Re: incorrect PHP code "Christoph M. Becker" <cmbecker69@arcor.de> - 2018-01-18 17:18 +0100
Re: incorrect PHP code nospam@ms.com - 2018-01-18 17:01 +0000
Re: incorrect PHP code "Christoph M. Becker" <cmbecker69@arcor.de> - 2018-01-18 18:18 +0100
Re: incorrect PHP code nospam@ms.com - 2018-01-18 17:30 +0000
Re: incorrect PHP code "Christoph M. Becker" <cmbecker69@arcor.de> - 2018-01-18 18:37 +0100
PHP forums (was: incorrect PHP code) Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2018-01-18 19:27 +0100
Re: PHP forums (was: incorrect PHP code) Tim Streater <timstreater@greenbee.net> - 2018-01-18 22:09 +0000
Re: incorrect PHP code Jerry Stuckle <jstucklex@attglobal.net> - 2018-01-18 22:01 -0500
Re: incorrect PHP code Jerry Stuckle <jstucklex@attglobal.net> - 2018-01-18 22:06 -0500
Re: incorrect PHP code Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2018-01-18 19:08 +0100
Re: incorrect PHP code Arno Welzel <usenet@arnowelzel.de> - 2018-09-05 09:40 +0200
Re: incorrect PHP code inigojoseph89@gmail.com - 2018-01-22 23:07 -0800
Re: incorrect PHP code Jerry Stuckle <jstucklex@attglobal.net> - 2018-01-23 07:53 -0500
Re: incorrect PHP code careenjoseph36@gmail.com - 2018-03-06 01:49 -0800
csiph-web