I'm going through the Help Center on our recently-purchased Google
Mini. I have a section of content I need to index for only that
section. The problem is, I can't, through my own code, give the Google
Mini access via its IP address. So I did some digging and found out
about Cookie Sites, but I can't access that feature on the Google
Mini, same with using the search suggestions feature.
Do I really have to shell out $30,000+ for an enterprise box in order
to do this?
Cause if so, then our reason for purchasing the latest Mini (multi-
collections & front-ends) was completely wrong, even more so because
my company won't sign off on purchasing a $30k box. We could've stuck
with our old Google Mini and not spent the $3,000 on the new one.
Thanks for any info, I couldn't find any through datasheets.
In that case, I guess you will have to build those 2 features on your
own. For example, you can set up a proxy server to handle the cookie
authentication part, and have the Google Mini crawl via the proxy.
There may be an even easier approach, depending on how your website is
set up. For example, if the cookies are not dynamic, and do not
change over time, you can include the static cookie information in the
HTTP header. This will allow the website to recognize the Google Mini
as an authorized user, and allow it to crawl the content.
As for the suggestions feature, you will need to set up something,
perhaps on your web server, to offer the suggestions, and modify the
search frontends to receive and show them.
On Nov 7, 8:08 am, Kinsbane <kinsb...@gmail.com> wrote:
> I'm going through the Help Center on our recently-purchased Google
> Mini. I have a section of content I need to index for only that
> section. The problem is, I can't, through my own code, give the Google
> Mini access via its IP address. So I did some digging and found out
> about Cookie Sites, but I can't access that feature on the Google
> Mini, same with using the search suggestions feature.
> Do I really have to shell out $30,000+ for an enterprise box in order
> to do this?
> Cause if so, then our reason for purchasing the latest Mini (multi-
> collections & front-ends) was completely wrong, even more so because
> my company won't sign off on purchasing a $30k box. We could've stuck
> with our old Google Mini and not spent the $3,000 on the new one.
> Thanks for any info, I couldn't find any through datasheets.
> In that case, I guess you will have to build those 2 features on your
> own. For example, you can set up a proxy server to handle the cookie
> authentication part, and have the Google Mini crawl via the proxy.
> There may be an even easier approach, depending on how your website is
> set up. For example, if the cookies are not dynamic, and do not
> change over time, you can include the static cookie information in the
> HTTP header. This will allow the website to recognize the Google Mini
> as an authorized user, and allow it to crawl the content.
> As for the suggestions feature, you will need to set up something,
> perhaps on your web server, to offer the suggestions, and modify the
> search frontends to receive and show them.
> On Nov 7, 8:08 am, Kinsbane <kinsb...@gmail.com> wrote:
> > I'm going through the Help Center on our recently-purchased Google
> > Mini. I have a section of content I need to index for only that
> > section. The problem is, I can't, through my own code, give the Google
> > Mini access via its IP address. So I did some digging and found out
> > about Cookie Sites, but I can't access that feature on the Google
> > Mini, same with using the search suggestions feature.
> > Do I really have to shell out $30,000+ for an enterprise box in order
> > to do this?
> > Cause if so, then our reason for purchasing the latest Mini (multi-
> > collections & front-ends) was completely wrong, even more so because
> > my company won't sign off on purchasing a $30k box. We could've stuck
> > with our old Google Mini and not spent the $3,000 on the new one.
> > Thanks for any info, I couldn't find any through datasheets.
> I can setup the cookie info in HTTP header in the Google Mini admin
> page, right?
> On Nov 6, 4:26 pm, Andy Wu <andywu200...@gmail.com> wrote:
> > In that case, I guess you will have to build those 2 features on your
> > own. For example, you can set up a proxy server to handle the cookie
> > authentication part, and have the Google Mini crawl via the proxy.
> > There may be an even easier approach, depending on how your website is
> > set up. For example, if the cookies are not dynamic, and do not
> > change over time, you can include the static cookie information in the
> > HTTP header. This will allow the website to recognize the Google Mini
> > as an authorized user, and allow it to crawl the content.
> > As for the suggestions feature, you will need to set up something,
> > perhaps on your web server, to offer the suggestions, and modify the
> > search frontends to receive and show them.
> > On Nov 7, 8:08 am, Kinsbane <kinsb...@gmail.com> wrote:
> > > I'm going through the Help Center on our recently-purchased Google
> > > Mini. I have a section of content I need to index for only that
> > > section. The problem is, I can't, through my own code, give the Google
> > > Mini access via its IP address. So I did some digging and found out
> > > about Cookie Sites, but I can't access that feature on the Google
> > > Mini, same with using the search suggestions feature.
> > > Do I really have to shell out $30,000+ for an enterprise box in order
> > > to do this?
> > > Cause if so, then our reason for purchasing the latest Mini (multi-
> > > collections & front-ends) was completely wrong, even more so because
> > > my company won't sign off on purchasing a $30k box. We could've stuck
> > > with our old Google Mini and not spent the $3,000 on the new one.
> > > Thanks for any info, I couldn't find any through datasheets.
> On Nov 7, 2:26 am, Kinsbane <kinsb...@gmail.com> wrote:
> > Thanks for the info, Andy.
> > I can setup the cookie info in HTTP header in the Google Mini admin
> > page, right?
> > On Nov 6, 4:26 pm, Andy Wu <andywu200...@gmail.com> wrote:
> > > In that case, I guess you will have to build those 2 features on your
> > > own. For example, you can set up a proxy server to handle the cookie
> > > authentication part, and have the Google Mini crawl via the proxy.
> > > There may be an even easier approach, depending on how your website is
> > > set up. For example, if the cookies are not dynamic, and do not
> > > change over time, you can include the static cookie information in the
> > > HTTP header. This will allow the website to recognize the Google Mini
> > > as an authorized user, and allow it to crawl the content.
> > > As for the suggestions feature, you will need to set up something,
> > > perhaps on your web server, to offer the suggestions, and modify the
> > > search frontends to receive and show them.
> > > On Nov 7, 8:08 am, Kinsbane <kinsb...@gmail.com> wrote:
> > > > I'm going through the Help Center on our recently-purchased Google
> > > > Mini. I have a section of content I need to index for only that
> > > > section. The problem is, I can't, through my own code, give the Google
> > > > Mini access via its IP address. So I did some digging and found out
> > > > about Cookie Sites, but I can't access that feature on the Google
> > > > Mini, same with using the search suggestions feature.
> > > > Do I really have to shell out $30,000+ for an enterprise box in order
> > > > to do this?
> > > > Cause if so, then our reason for purchasing the latest Mini (multi-
> > > > collections & front-ends) was completely wrong, even more so because
> > > > my company won't sign off on purchasing a $30k box. We could've stuck
> > > > with our old Google Mini and not spent the $3,000 on the new one.
> > > > Thanks for any info, I couldn't find any through datasheets.
Be advised that adding any headers here overrides any automatic
headers that already exist. For instance, if there are dynamic
cookies as part of your security implementations, your GSA will cease
to be able to log in if you replace the cookie header.
|
