Bought Opera with IE
Jussi Piitulainen
purchase form at BMT Micro's site. Opera, Carbon beta on OS X, got
only the 400 Bad Request. IE worked without problems.
At least Opera 5 on OS 9 was able to submit the information about the
incident to the Opera Mac team. I also asked BMT Micro to look into
their logs to find out what the allegedly bad request was.
It may be just me, but now it is two different Opera browsers on two
different Mac operating systems on two different Macintosh computers,
repeatedly. Or maybe unreleased versions of the browser do not have
this problem - even the Carbon beta is half a year old. Any news?
--
Jussi
Bent Flyen
Jussi Piitulainen <jpii...@ling.helsinki.fi> wrote:
We have seen this problem and tried to find out what the problem is
together with BMT. We are not able to reproduce it consistenly and we
have not seen the problem on other servers...
--
BenT
Opera Mac Team
<http://www.opera.com/mac>
Jussi Piitulainen
> Jussi Piitulainen wrote:
[...]
>> different Mac operating systems on two different Macintosh
>> computers, repeatedly. Or maybe unreleased versions of the browser
>> do not have this problem - even the Carbon beta is half a year old.
>> Any news?
>
> We have seen this problem and tried to find out what the problem is
> together with BMT. We are not able to reproduce it consistenly and
> we have not seen the problem on other servers...
It's weird. They do log these errors, do they?
--
Jussi
Erik Sandblom
jpii...@ling.helsinki.fi den 02-08-19 16.04:
I'd be surprised if they don't. Bent's reply suggests they do log the errors
and they were able to reproduce the problem, ie they got it too, but
sometimes it worked fine. Since they don't know what's wrong, it's hard to
fix it.
It seems the Opera guys are working on the embeddable Mac version for
Macromedia. I hope once that is done they will work on MacOpera 6. On the
other hand, if they have been working all summer they might want to take
some time off...
--
Erik Sandblom
my site is EriksRailNews.com
for those who don't believe, no explanation is possible
for those who do, no explanation is necessary
Bent Flyen
Erik Sandblom <sand...@artech.removethis.andthis.se> wrote:
> I'd be surprised if they don't. Bent's reply suggests they do log the errors
> and they were able to reproduce the problem, ie they got it too, but
> sometimes it worked fine. Since they don't know what's wrong, it's hard to
> fix it.
>
> It seems the Opera guys are working on the embeddable Mac version for
> Macromedia. I hope once that is done they will work on MacOpera 6. On the
> other hand, if they have been working all summer they might want to take
> some time off...
We will not take some time off, and you can look forward to a beta
release that includes the Opera core as a shared library. It will be the
first desktop version of Opera with the Opera core as a shared library.
And you will also get most of the Opera 6.0 features from the Windows
and Linux versions :-)
Planned release date is after the release of MacOS 10.2 and this time it
will be distributed as a disk image. Opera 6.0 for Mac is a Carbon
application and it has been tested under 9.1, 9.2.2, 10.1.5 and 10.2. We
are now starting testing under 8.6.
egilDOTnet
I hope it will be released IMMEDIATELY after the jaguar release - I am
dying for a new Opera...!
--
-(e)-
Tim Altman
wrote:
[...]
>We will not take some time off, and you can look forward to a beta
>release that includes the Opera core as a shared library. It will be the
>first desktop version of Opera with the Opera core as a shared library.
Bent, do you mean that you'll be able to embed Opera in other
programs running on the Mac?
--
Tim Altman
roy...@myrealSP-AMbox.com
No SP-AM is good spam.
Bent Flyen
Tim Altman <add...@in.sig> wrote:
> On Tue, 20 Aug 2002 14:29:52 +0200, Bent Flyen <bfl...@opera.com>
> wrote:
>
> [...]
>
> >We will not take some time off, and you can look forward to a beta
> >release that includes the Opera core as a shared library. It will be the
> >first desktop version of Opera with the Opera core as a shared library.
>
> Bent, do you mean that you'll be able to embed Opera in other
> programs running on the Mac?
Correct :-)
egilDOTnet
--
-(e)-
Rogerio Brito
> Planned release date is after the release of MacOS 10.2 and this time
> it will be distributed as a disk image. Opera 6.0 for Mac is a Carbon
> application and it has been tested under 9.1, 9.2.2, 10.1.5 and
> 10.2. We are now starting testing under 8.6.
This are some excellent news! It is nice to know that I will be able to
use Opera for MacOS X 10.1 with tab (I suppose that that's included),
because it is quite funny to have Opera for Linux on PowerPC with tabs
and Opera for MacOS X without them. :-)
Anyway, those are some nice news!
Thanks for your work, Roger...
Jussi Piitulainen
> We will not take some time off, and you can look forward to a beta
Just don't burn yourselves out.
> Planned release date is after the release of MacOS 10.2 and this
> time it will be distributed as a disk image. Opera 6.0 for Mac is a
> Carbon application and it has been tested under 9.1, 9.2.2, 10.1.5
> and 10.2. We are now starting testing under 8.6.
This is excellent news. Thanks.
--
Jussi
Jussi Piitulainen
> i artikel qot65y7...@venus.ling.helsinki.fi, skrev Jussi
> Piitulainen på jpii...@ling.helsinki.fi den 02-08-19 16.04:
>
>> Bent Flyen writes:
>>> We have seen this problem and tried to find out what the problem
>>> is together with BMT. We are not able to reproduce it consistenly
>>> and we have not seen the problem on other servers...
>>
>> It's weird. They do log these errors, do they?
>
> I'd be surprised if they don't. Bent's reply suggests they do log
> the errors and they were able to reproduce the problem, ie they got
> it too, but sometimes it worked fine. Since they don't know what's
> wrong, it's hard to fix it.
Yes, I understood that they were able to reproduce it, and that it was
not consistent (it has not been for me either).
But I don't see any suggestion about what they log, and I do not know
what is standard practice here. I mean, is the offending request
itself available somewhere for the developers to see? Just wondering
whether the browser sent something bad or whether the server was
dense. (I understand that the request must not be shown to outsiders
like me in any case, as it would contain my credit card number.)
But I'll stop worrying about this now. (It is a weird problem,
though.)
--
Jussi