Ok, removed the broken links. Too bad we have no active demo servers.
On Thu, Nov 24, 2016 at 2:08 PM Yuri Z <vega...@gmail.com> wrote:
> Ok, I ll find the time to remove broken/invalid links.
>
> On Tue, Oct 4, 2016 at 11:21 PM Zachary Yaro <zmy...@gmail.com> wrote:
&g
Ok, I ll find the time to remove broken/invalid links.
On Tue, Oct 4, 2016 at 11:21 PM Zachary Yaro <zmy...@gmail.com> wrote:
> WaveInABox.net used to host an Apache Wave demo instance, but presumably
> the domain expired and someone else bought it up. Those links were correct
&
WaveInABox.net used to host an Apache Wave demo instance, but presumably
the domain expired and someone else bought it up. Those links were correct
at the time they were added, but they should probably be removed now.
Zachary Yaro
On Tuesday, 4 October 2016, Philip McGrath <
I'm not sure if this is the right place to report this, but I wanted to let
you know that http://waveinabox.net doesn't currently appear to have
anything to do with Wave. I found links to it from
http://incubator.apache.org/wave/about.html and
http://incubator.apache.org/wave/demo-servers.html
Hi
The waveinabox.net demo server is back online.
Having federation uprunning (see previous email), I'm currently running
tests federating with the other 2 wave servers with varying results.
Specifically:
* Federating with waveinabox.net: upon first delta, I received a failure to
validate cert info; this seems to be either due to lack of SSL
with the other 2 wave servers with varying results.
Specifically:
* Federating with waveinabox.net: upon first delta, I received a failure
to validate cert info; this seems to be either due to lack of SSL, or lack
of cert caching. Full stackdump at http://pastebin.com/S71UXg4V .
* Hacking
The certificates for waveinabox.net are outdated, so no wonder there's
problem. Even if you hacked your server, there's still verification on
waveinabox.net which probably causes problems.
I'm in the process of re-structuring the wave server deployment for
waveinabox.net so don't have the time
Yeah, federation is not something we ever worked on, it's more or less as
it was in fedone. Anyway, wave is not ready enterprise use yet for more
reasons.
On Sun, Aug 31, 2014 at 11:31 PM, Yuri Z vega...@gmail.com wrote:
The certificates for waveinabox.net are outdated, so no wonder there's
:
By the way, today I can login to waveinabox.net form the office. It
looks
like an issue with browsers getting correct proxy configuration...
On Wed, Apr 4, 2012 at 5:31 PM, Ben Hegarty heg...@gmail.com wrote:
Is there any way that we can change wiab to operate behind company
firewalls
:
El 03/04/12 15:55, Yuri Z escribió:
Today the company that I am working for installed
WebSensehttp://www.websense.comand as result
waveinabox.net stopped working for me on office computers. micro-box
still
works.
Hi Yuri:
Maybe
- you can try to enable ssl in waveinabox
By the way, today I can login to waveinabox.net form the office. It looks
like an issue with browsers getting correct proxy configuration...
On Wed, Apr 4, 2012 at 5:31 PM, Ben Hegarty heg...@gmail.com wrote:
Is there any way that we can change wiab to operate behind company
firewalls/proxys
Today the company that I am working for installed
WebSensehttp://www.websense.comand as result
waveinabox.net stopped working for me on office computers. micro-box still
works.
On Thu, Mar 29, 2012 at 8:27 PM, Yuri Z vega...@gmail.com wrote:
Another related case: https://issues.apache.org/jira
El 03/04/12 15:55, Yuri Z escribió:
Today the company that I am working for installed
WebSensehttp://www.websense.comand as result
waveinabox.net stopped working for me on office computers. micro-box still
works.
Hi Yuri:
Maybe
- you can try to enable ssl in waveinabox:
- or in your office
Hey Guys,
I've been using this server as a kind of reference server for making sure
that issues in my own server setup are actually my own. I've tried a new
account and multiple browsers but I always just get 'a turbulance
detected', I'm seeing similar issues on my own server and thought that this
At the moment I can only try from behind a proxy, I'll try again tonight
when I have a direct internet connection.. Cheers
On Thu, Mar 29, 2012 at 11:04 AM, Yuri Z vega...@gmail.com wrote:
described
I have that problem with Chrome, but works fine with Firefox?
--
Juan Fernandez
Corporate IT Infrastructure and Support
The GBS Group
397 Little Neck Rd.
Building 3300 South, Suite 204
Virginia Beach, VA. 23452
Office: (757)965-4274 | Fax: (757)965-4518 | Cell: (757)705-4196
www.theGBSgroup.us
I have had the issue Juan Fernandez described on some computers on my
school's wired network. Interestingly, I have no issues on the wireless
network, which is significantly *more* restricted, so I do not think it is
an issue with proxies or blocked ports (if this is even the same issue—I do
not
I discovered some errors related to Socket.IO in waveinabox.net server log
and would like to report them. They all seem to be connected with Firefox
socket connection.
The first error looks like this:
643:DBUG::REQUEST /socket.io/xhr-multipart
19 matches
Mail list logo
