Current version: Webuilder 9.4.1.130 on XP Pro SP3.
I've had a long term problem with Webuilder (& previously Rapid PHP) in that I've not been able to get preview working properly.
The only method that works has been to install Apache on the same machine as Webuilder, which I don't think should be required when I have a dedicated web server in house on the same subnet.
I've previously done a couple of complete re-installs from scratch (Reformat & install everything from scratch), but this has not cured the problem.
I have just done this again and, temporarily, the preview using the built-in webserver worked! - for a couple of days.
It then packed up again, and this time I think I may know why - something does not like IPV6!
When I now try to preview, the address shown is [::1] which is IPV6 shorthand for localhost.
Using command-line ping from a dos box, pinging localhost uses IPV6 notation, if I ping 127.0.0.1 explicitly I get IPV4 notaton.
When I try a preview in IE7, the URL line includes 'localhost' and nothng happens.
If I change 'localhost' to '127.0.0.1' I get the preview!
It appears to be a generic problem with IPV6, there is reference to a similar problem using Microsoft's own embedded web server in Visual Studo -
http://social.msdn.microsoft.com/Forums ... 945aad23f/
Note the only reference to 'localhost' in my Hosts file is the IPV4 one, I guess the ::1 is hardcoded somewhere in the XP V6 stack..
Is there any way to make the internal preview use 127.0.0.1 rather than localhost in the preview URL?
Thanks,
Robert.
Webuilder - Preview bug if IPV6 enabled?
Moderator: kfury77
Forum rules
Please try to follow these guidelines. This will help to receive faster and more accurate response.
Please try to follow these guidelines. This will help to receive faster and more accurate response.
- Check the Support section of the corresponding product first. Chances are you will find your answer there;
- Do not create new topics for already reported problems. Add your comments to the existing topics instead;
- Create separate topic for each problem request. Do NOT post a number of non-related problem reports in a single topic;
- Give your topic a meaningful title. Titles such as "A question," "Bug report" and "Help!" provide others no clue what your message is about;
- Include the version number of the software you are using;
- This is not an official customer support helpdesk. If you need a prompt and official response, please contact our support team directly instead. It may take a while until you receive a reply in the forum;
Webuilder - Preview bug if IPV6 enabled?
Robert Jenkins
-
Karlis
- Site Admin
- Posts: 3605
- Joined: Mon Jul 15, 2002 5:24 pm
- Location: Riga, Latvia, Europe
- Contact:
Re: Webuilder - Preview bug if IPV6 enabled?
I wonder why were you unable to run the preview on the remote server? Probably you did not take in account the fact that mappings should be configured AND the files must be saved and uploaded PRIOR to opening preview.
E.g. you have dedicated server path for your project say http://192.x.x.x/myweb/ and you have your project folder where you edit files before publishing them, say c:\webprojects\myweb\ , here is what you have to do:
1) Add mapping and map http://192.x.x.x/myweb/ to c:\webprojects\myweb\ OR http://192.x.x.x/ to c:\webprojects\
2) Every time you want to preview the file, before previewing, save and upload the file to server, then use preview.
It is important to understand that WeBuilder can not read minds, so you must tell exactly which folder maps to which remote path in case of a remote server and make sure the files are there.
---
Unfortunately at the present moment there is no way to work around "localhost", in fact, you are the first customer to have problem with this (because of Microsoft, so no blame). I wonder how widespread this problem is?
E.g. you have dedicated server path for your project say http://192.x.x.x/myweb/ and you have your project folder where you edit files before publishing them, say c:\webprojects\myweb\ , here is what you have to do:
1) Add mapping and map http://192.x.x.x/myweb/ to c:\webprojects\myweb\ OR http://192.x.x.x/ to c:\webprojects\
2) Every time you want to preview the file, before previewing, save and upload the file to server, then use preview.
It is important to understand that WeBuilder can not read minds, so you must tell exactly which folder maps to which remote path in case of a remote server and make sure the files are there.
---
Unfortunately at the present moment there is no way to work around "localhost", in fact, you are the first customer to have problem with this (because of Microsoft, so no blame). I wonder how widespread this problem is?